Skip to main content

Workspace Tabs and Plan Gates Reference

Workspace settings are organized into functional tab groups. Some tabs are plan-gated.

Tab groups at a glance

Workspace

  • General
  • Members
  • Billing
  • Domains (plan-gated)

Integrations

  • Webhooks (plan-gated)
  • Tracking (plan-gated)
  • Stripe (plan-gated)

Communication

  • Emails

Developer

  • API Keys (plan-gated)
  • API Apps (plan-gated)
  • Embeds (plan-gated)

Security

  • Security / SAML / SCIM controls (enterprise-gated)

Plan-gate behavior model

If a feature is not included in the active plan:
  • tab can be hidden or unavailable.
  • related UI actions are blocked.
  • API operations for gated features should be restricted consistently.

Tab reference

TabPurposeTypical actions
GeneralWorkspace identity and defaultsName, branding, default preferences
MembersTeam access lifecycleInvite, role updates, remove members
BillingPlan and payment operationsPlan changes, invoices, usage visibility
DomainsBranded domainsAdd/verify/remove custom domains
WebhooksEvent delivery operationsConfigure destinations, secrets, retries
TrackingTracking controlsPublishable keys and tracking behavior
StripeRevenue integrationsMerchant/connect settings and sync options
EmailsEmail history/auditInspect email delivery and recent sends
API KeysServer automation credentialsCreate scoped keys and rotate
API AppsOAuth app credentialsClient ID/secret, redirect URI management
EmbedsPublic embed controlsGenerate/manage embed snippets
SecurityEnterprise identity controlsSSO/SAML/SCIM and security governance

Operational checklist after plan change

  1. Re-check visible workspace tabs.
  2. Re-check automation using gated features.
  3. Re-check integrations relying on gated modules.
  4. Re-check team permissions and ownership assignment.

Common confusion points

QuestionClarification
Why is a tab missing?Usually plan gate or permission role limit
Why did a feature stop after downgrade?Downgrade can disable gated modules
Why can one admin see a tab and another cannot?Role and workspace context both matter
Related:
  • /user-guides/manual/workspace/workspace-onboarding-and-governance-playbook
  • /user-guides/manual/workspace/workspace-settings-and-governance-reference
  • /user-guides/manual/workspace/workspaces-and-access
  • /user-guides/manual/monetization/plans-pricing-and-limits-reference