Understand enabled modules, limits, and billing

Distinguish a disabled capability from an access restriction or plan limit.

Your organization’s enabled modules and plan limits affect which features are available. These checks are separate from a person’s permissions.

If a feature is locked, read the reason shown: the module may be disabled, a dependency may be missing, the current plan may impose a limit, or your account may lack permission.

Use the organization’s module controls to review enabled features. Canvas types also show module requirements: Design uses Work Design, Automation uses Automation + DevTools, and Telemetry uses Telemetry & Systems.

Open Billing & Usage to see the current plan and trial information shown for the organization. Use the subscription-management action when available to open the billing provider’s portal.

Use the product’s current plan display for names, limits, and charges. Help articles should not substitute an outdated pricing table or promise that enabling a module grants people access to its data.

When a member limit blocks onboarding

The effective member allowance can differ by workspace, including an individually configured allowance. Check the selected organization and the limit shown by the product; do not infer its allowance only from a generic plan table.

If an invitation or acceptance is blocked at the member limit, ask the workspace administrator to review current membership and the applicable subscription arrangement. The reviewed change does not add a self-service field where every administrator can enter a new limit. Do not remove an active colleague simply to retry an invitation without first arranging the handover.