#Portal Guides

2 min read

Audience-facing portal usage guides live here. These guides explain how to use the portal, understand your access, and find the right customer or partner workflow.

#Guide Sections

  • Client Guides — primary customer-facing guide set for Getting Started, Dashboard (labelled Overview in the portal), Calls, Support, Billing, Settings, your own Account profile and security, Compliance, Activity Log, System Status, Role Reference, and Troubleshooting. Team and user changes are made by your AiDial partner outside the customer portal — see Team and User Management.
  • Partner Guides — partner-facing guide set for Partner Team, Clients, API Keys, Projects, Outbound Campaigns, Integrations, Analytics & Usage, and Escalation Boundaries.

Both guide sets are published. Several portal routes are shared between customer and partner roles — Dashboard, Calls, Settings, System Status, Activity Log, and Support — so they are documented once in the client guides and linked from the partner guides rather than duplicated. A shared route does not always mean a shared page: /dashboard and /status render a partner-specific view for partner roles, so partners should use the Partner Guides for those two. Billing is also a shared page, but it is available to partner_admin only.

#Access Notes

  • The portal re-checks your signed-in role and organisation scope on the server for every protected request, not only when a menu item is rendered.
  • Navigation visibility is a convenience, not a security boundary. Opening a direct link outside your role or organisation scope returns a not-found style response that does not reveal whether the page or another organisation exists.
  • Sign-in and account-level problems are handled separately: an unrecognised role, an incomplete sign-in, or a suspended organisation lands on the access-denied page with a reason instead.
  • Partner users may see some shared customer guides when the same portal page behaviour applies to partner roles.