Platform Admin
The cross-organization control room for whoever runs the deployment — organizations, users, access requests, sales leads, pricing, roles and system health.
Everything in the rest of these docs describes what a customer sees inside their own organization. Platform Admin is the other side: one place for whoever operates the deployment to see across every organization on it.
On Talkr Cloud that operator is us. On your own deployment, it's you.
You'll find it at /superadmin, and it's visible only to accounts with platform superuser status. Everyone else is redirected away — the portal doesn't appear in navigation, and its pages return nothing without that status.
What's in it
| Section | What it's for |
|---|---|
| Dashboard | Live totals across the deployment — organizations, users, calls, credit consumption |
| Organizations | Every tenant, their plan and credit balance, with the ability to adjust credits or set enterprise metadata |
| Users | Every account, and the ability to grant or revoke superuser status |
| Requests | Access requests, SSO configuration requests, and connector access requests awaiting a decision |
| Leads | Enquiries from the marketing site's contact forms |
| Invites | Platform invitations that create a brand-new organization and its first owner |
| Connectors | OAuth app configuration and connector health across all tenants |
| Billing and Pricing | Transactions, and the credit rates and top-up packs the whole deployment runs on |
| Audit Log | The cross-organization trail, including platform-scoped events no single tenant can see |
| Phone Numbers | Every number across every tenant, and which agent answers it |
| Workflow Runs | Cross-tenant call history for debugging |
| Impersonate | Sign in as a specific user to reproduce a support issue — recorded in that customer's own audit log |
| System Health | Database, Redis, storage and worker checks |
| Feature Flags | Turn capabilities on per organization without a deploy |
| Roles | The permission matrix behind every role in every organization |
Leads
Leads collects enquiries from the two forms on the marketing site:
- Book a Strategy Call — the enterprise enquiry form
- Let us build your voice agent — the done-for-you build request
Every submission is written to the database the moment it arrives. A copy is also emailed to your sales address, but that email is deliberately best-effort: if it fails — an expired API key, a spent daily sending quota, a provider outage — the enquiry is still safely recorded and still appears here. This page is the reliable record; the email is the convenience.
Reading a lead
The table shows the essentials at a glance — when it arrived, who sent it, their company, and their expected call volume. Email addresses and phone numbers are live links, so you can start a reply without retyping anything.
Click any row to expand the rest: their job title, preferred deployment model, country and timezone, which page the form was submitted from, and — most useful of all — what they actually want to build, in their own words.
Finding one
Filter by form to separate strategy-call enquiries from build requests. Search matches name, company, or email address, case-insensitively, so a half-remembered detail is enough to find someone.
The queue is paginated and always newest-first. Leads are never deleted or archived automatically, so the full history stays available.
Leads are enquiries from members of the public, so they contain personal data — names, work emails, phone numbers. Access is restricted to platform superusers, and leads are never visible to any customer organization. Handle exports and retention in line with whatever privacy commitments your deployment makes.
Workflow Runs
Workflow Runs is the call history for every organization on the deployment, in one list — the place to go when a customer reports a problem with a specific call.
It carries the same filters a customer has on their own run list, plus one only available here: Organization. Pick tenants by name from a searchable list — one when investigating a single report, several to compare them side by side. Stack it with a date range, a disposition or a call tag to go straight to the calls in question.
Runs stay with the organization that owns the agent, so a tenant's history remains complete and stable even as the people who build their agents come and go.
Adjusting an organization's credits
Open Organizations, find the tenant, and adjust their credit balance in place. Enter a positive number to add credits or a negative one to deduct.
Every adjustment is written to the credit ledger alongside the organization's normal call usage, so the balance always has a full history behind it, and the change is recorded in the audit log against the superuser who made it.
The trial grant — the credits every brand-new organization starts with — is set once under Pricing and applies to each organization created from then on, so you can size the free evaluation to your deployment rather than topping up accounts one at a time.
Granting platform access
Superuser status is granted from Users, by an existing superuser.
On a brand-new deployment there is no one to do that yet, so the very first superuser has to be promoted with a single direct database update. Every promotion after that goes through the portal, and each one is recorded in the audit log.
Superuser status is deployment-wide. It reads across every organization's data and can adjust credits, change pricing and impersonate users. Grant it to as few accounts as the job needs.