Sign in with an individual account
Choose the right sign-in, accept an invitation, and securely reset your Voice AI portal password.
Sign in with an individual account
Which sign-in should I use?
| Who you are | Sign-in path | Where it takes you |
|---|---|---|
| Platform Admin | Go to Platform Admin sign-in and use your Platform Admin email and password. | /admin, with platform-wide access |
| Organization Admin | Go to the MakeAutomation sign-in or an authorized branded /login, choose Individual account, and use your invited email and password. | /admin, for the organization and client portals in your assigned scope |
| Organization Operator | Use /login and choose Individual account. | /admin, for day-to-day work in the organization scope assigned to you; no team-access management |
| Partner Admin | Use /login and choose Individual account. | /admin, for the assigned partner and its client portals, including team management in that scope; cannot create partner organizations |
| Partner Operator | Use /login and choose Individual account. | /admin, for day-to-day work in the assigned partner scope; no team-access management |
| Client Portal User | Use /login and choose Individual account. | /portal, for the client portal assigned to that email |
| Legacy shared API-key portal user | Use /login, choose API key, and enter the shared tenant API key. | /portal, when API-key portal sign-in is enabled for that tenant |
Use the canonical MakeAutomation sign-in unless your administrator gave you an authorized branded sign-in address. A branded address changes the sign-in page, not your permissions.
The Individual account choice is available only when identity sign-in is enabled. If you have an invitation but do not see it, contact your administrator instead of using API key. Client Portal Users also need individual sign-in enabled for their client portal. The API key choice may still appear, but shared portal sign-in succeeds only when the tenant's effective portal mode permits it.
API integrations that send X-API-Key use an API endpoint. They are not a
browser sign-in choice and are not changed when a portal moves to individual
accounts.
Understand the names
- A tenant is one client's Voice AI workspace. It contains that client's agents, calls, and portal.
- An organization is the top-level customer or commercial account. It can contain its own tenants and, when needed, partners with their tenants.
- A partner is a reseller or delegated team inside one organization. It can contain tenants, but not another partner or organization.
The supported paths are organization → tenant and organization → partner → tenant. A tenant is still the end-client workspace in either path.
Accept your invitation
- Open the invitation email within 72 hours.
- Select Accept invitation.
- Choose a password between 12 and 128 characters and confirm it.
- Go to your sign-in page, choose Individual account, and enter your email and password.
Organization and partner staff return to this same sign-in page when their session expires. The separate Platform administrator sign-in link is only for the MakeAutomation Platform Admin.
Organization and partner staff may sign in from a branded domain for a client portal in their scope. They may also use a domain for a tenant owned directly by their top-level organization when it serves as a same-root staff gateway. Portal sessions remain bound to that exact tenant. A branded host never grants additional access, and Platform Admins use the canonical MakeAutomation domain.
If your staff identity has memberships in more than one top-level organization, the sign-in page asks which organization to enter. Each choice is a separate access context: staff roles and permissions in one organization never carry into another. Sign out and sign in again to change organization.
A Client Portal User email should be assigned in only one organization at a time. If sign-in offers you multiple organizations or the wrong client portal appears, stop, sign out, and ask your administrator to correct your access.
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 Portal User email should be assigned to one client portal in one top-level organization at a time. Organization Admins and Partner Admins create access through the 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 a different portal, ask an administrator to review and correct your assignment—do not share accounts. If the sign-in page offers more than one organization or opens the wrong portal, sign out and contact your administrator before continuing.
During a hybrid transition, individual account and shared API-key portal
sign-in can both work. When individual accounts become required, new API-key
portal sign-ins and old shared portal sessions stop working. This does not
change API integrations that use X-API-Key or embedded/GHL portal access.
Follow your administrator's instructions if sign-in availability changes.
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 Portal Users cannot reveal or copy keys. Do not put a key in a URL, chat, ticket, screenshot, or saved browser field.
Reset your password
- On the sign-in page choose Individual account and enter your email.
- Select Forgot password?
- Open the reset email within one hour.
- 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.