Sign in with an individual account

Individual-account access is enabled separately for each client portal through a controlled canary rollout. Your administrator will notify you when your portal is ready. Invitations can be accepted before portal identity sign-in is enabled, so a temporary “not enabled” message after acceptance is expected during staging. No tenant is cut over automatically.

Accept your invitation

1. Open the invitation email within 72 hours.
2. Select Accept invitation.
3. Choose a password between 12 and 128 characters and confirm it.
4. Go to the sign-in page, choose Individual account, and enter your email and password.

If your identity belongs to more than one organization, the sign-in page asks which organization you want to enter. Each choice is a separate access context: your role and permissions in one organization never carry into another. Sign out and sign in again to change organization.

Invitation links work once. Ask your administrator to resend the invitation if it expired or was already used. For safety, support cannot inspect or recover the invitation token.

Client portal access

A Client Tenant User is assigned to one exact client portal. After sign-in you are taken directly to that portal. Organization and partner administrators create access through this same invitation flow after a tenant is provisioned. The access form uses organization, partner, and client portal names; administrators do not need internal IDs. Tenant credentials and infrastructure settings are never included in delegated provisioning responses or emails. If you need another tenant, ask an administrator to review your assignment—do not share accounts.

During a hybrid transition, both the existing portal API key and individual accounts work. Once your administrator completes the transition, new API-key portal sign-ins and old shared portal sessions stop working and the sign-in page asks for an individual account. This does not change API integrations that use X-API-Key. Embedded/GHL portal access also remains available. If emergency compatibility mode is activated, individual sign-in is temporarily unavailable and your administrator will provide instructions.

Switch between permitted tenants

Organization and partner staff can open Organizations to browse the current hierarchy. Use the directory search to find an organization, partner, or client portal by name, then select the matching organization or partner to see its direct client portals. The Organizations and Partners filters narrow a large directory without changing your access. Select a client portal from the detail panel to open it.

The Tenant overview dashboard also shows every client workspace in scope, grouped by organization, with its status and voice-agent count. Search by tenant, slug, or organization, then choose Open to enter that workspace.

Use Operational tenant in the navigation for faster switching from any page. Type in the picker to filter a long list, use the arrow keys to move, and press Enter to select. The menu shows ten tenants before it scrolls. The selection is only a navigation preference; access is checked again on every page. If your scope changes or a tenant becomes inactive, the console automatically falls back to a remaining permitted tenant or shows that none are available.

Tenant API keys remain masked on lists and details. Authorized staff can use the short-lived Reveal or Copy action when operational access requires it; each action is audited before the key is shown. Client Tenant Users cannot reveal or copy keys. Do not put a key in a URL, chat, ticket, screenshot, or saved browser field.

Reset your password

1. On the sign-in page choose Individual account and enter your email.
2. Select Forgot password?
3. Open the reset email within one hour.
4. Choose a new password.

The confirmation message is intentionally the same for every email address. This protects account privacy. Check spam and ask your administrator to confirm your account is active if no message arrives.

Link safety

Invitation/reset links contain the secret after #token=. The portal removes it from browser history immediately and never sends it in a page URL or referrer. Do not paste these links into support tickets, chat, analytics tools, or screenshots.