Skip to main content
Navigation permissions control the sections available in an account’s portal. They are separate from membership, user roles and API-key permissions.

​
Set the account navigation

  1. In Accounts, open the account’s navigation-permissions action.
  2. In Navigation permissions, select the sections the client should use.
  3. Review the warning about replacing the account’s current configuration, then select Save changes.
  4. Open the portal with an account-only user and check its navigation and intended pages.
Workspace members receive the full navigation view in the portal. Checking only with your agency login can therefore hide the effect of these settings. Use an account-only test user to review the client experience.

​
Available switches

Each switch includes or removes its named portal section for account-only users. A selected section can still require the appropriate account type, membership, integration, or feature availability. The starting selection comes from the account’s saved configuration or workspace defaults. Review it instead of assuming all switches are on. Selecting Automations, for example, does not override that feature’s separate availability restrictions.

​
Set defaults for future accounts

Open Defaults → Features. Save the defaults for new accounts, or use the separate apply-to-existing action only when you intend to overwrite existing account navigation choices. Review the confirmation and affected-account count.

​
Troubleshooting

If a client cannot see a section, confirm the account’s saved navigation and their membership. If an agency user still sees it, check whether that user also has workspace access. If a route returns the user to the account home, review the section’s navigation setting. Do not use hiding a tab as a replacement for removing a member, restricting an API key, stopping an assistant or ending an integration. Those controls have separate purposes. See user management, account defaults, and v3 authentication.