#Clients
The Clients page is the partner view for assigned or partner-managed client accounts. Partner administrators can provision client profiles and assign active same-organisation partner members to clients. Partner users can view assigned clients in read-only mode.
#Who Can Use It
| Role | Access |
|---|---|
partner_admin | View clients, provision client profiles, and manage partner-member assignments for selected clients. |
partner_user | View assigned clients in read-only mode. |
Customer roles and internal AiDial roles do not use the partner Clients page.
#Client List
The client list supports search, lifecycle-status filtering, pagination, and client selection. Each row shows the client reference, customer-safe business name, domain or missing-domain state, contact email when the current role may see it, lifecycle/setup/billing/access summaries, project count, and last-activity state.
Client rows include quick links to Projects, Calls, Billing, and Integrations with the selected client_id in the URL. Those links are only context hints for the next surface; each destination still performs its own server-side client or project scope check.
A selected client panel appears only after you choose a row. It shows customer-safe business information such as business name, domain, and contact email when your role is allowed to see it.
Partner access is assigned server-side. The Clients list route does not accept browser-supplied client_id or tenant_id scope parameters, and client detail or downstream workflow routes deny out-of-assignment clients without revealing whether another tenant exists.
#Provisioning A Client
Partner administrators can create a client profile with:
- client ID
- business name
- web domain
- contact name
- business email
- timezone
Provisioning is submitted through the portal BFF and forwarded to aidial_api with the signed-in user's server-side bearer session. The current backend creates a provisioning-stage client profile, active partner ownership for the caller's partner organisation, and an active assignment for the creating partner administrator. It does not automatically create customer users, customer passwords, runtime telephony numbers, billing configuration, production runtime wiring, or production assistant deployment. Those follow their own approved workflows.
If a client profile needs data import, runtime wiring, billing setup, DNS, phone-number registration, or a production cutover, use Escalation Boundaries.
#Assigning Partner Users
Partner administrators can assign active same-organisation partner members to a selected client. The assignment panel lists currently assigned users and eligible users who can be added.
At least one support contact may be required to remain assigned. If removing a user would break that requirement, the portal rejects the removal. Removing your own client access requires an explicit confirmation before the request is sent.
Partner users see read-only client access and cannot assign or remove users.
#Scoping Rules
- Partner administrators see clients owned by their active partner organisation; partner users see only active client assignments.
- The current request context must also permit the client, including backend visibility checks.
- Out-of-assignment client IDs are denied without revealing whether another tenant exists.
- Partner users may see less contact detail than partner administrators.
- Other partner surfaces, such as billing, projects, calls, capacity, settings summaries, and integrations, still apply their own client or project scope checks.
#Not Self-Service
The partner Clients page does not replace AiDial operational workflows for:
- customer user creation or password recovery
- production call routing or phone-number provisioning
- billing-plan activation
- migration of historical call data
- customer contract or legal entity changes
- tenant deletion or restoration
Use Escalation Boundaries for those cases.