Admin overview
Intry internal operations, tooling, and responsibilities.
Overview
This section is for Intry employees and trusted operators who support customers, manage org-level settings, and monitor platform health.
Primary systems
| System | Usage |
|---|---|
Admin dashboard (tools/intry-admin) | Customer CRUD, call inspection |
Intry Ops (tools/intry-ops) | Tailscale-gated internal console |
Core API (/api/admin/*) | Automation + MCP |
| Railway / Fly dashboards | Deployments & logs |
| New Relic / Sentry / PostHog | Performance + product analytics |
| Chatwoot | Resident/PM AI support bots |
Access expectations
- Use SSO (WorkOS or Clerk) accounts with MFA.
- Tailscale for intry-ops access.
- Prefer least privilege Unkey keys for scripts.
- Never share operator credentials with customers.
Incident basics
- Acknowledge and assign an incident commander.
- Capture timestamps, tenant IDs, and carrier call SIDs (Twilio or Telnyx).
- Communicate via approved customer channels.
- Run a post-incident review with engineering.
Next steps
Developer docs: api-docs.gointry.com
Last verified: 2026-06-21 (commit 293c4a7)