CRM works in the selected company. A subscription feature does not grant staff permissions or access to another company's records. Your role, company membership, record ownership and field permissions still apply. An administrator can review roles and permissions.
Related video lesson
This chapter introduces the access boundaries; consult this guide for current capacity and downgrade behavior.
Check access before changing records
The tenant's purchased subscription and add-ons determine available features and capacity. Your subscription is the place to review that purchase. A plan name alone does not establish the tenant's current allowance. Features can also be temporarily paused during a rollout; a saved URL does not bypass that restriction.
Contacts, deals, organizations, open activities, pipelines, custom fields, quotes, reports, territories, modules and custom records have finite allowances. Imports also have row and concurrency limits. Files consume storage. Sequence and onboarding work uses shared workflow and schedule allowances. Enterprise capacity must be explicitly configured in the contract; Enterprise does not mean unlimited.
If an action is denied, check the selected company, your permissions, the enabled feature and the remaining capacity. Restoring records and creating related records can require capacity too. Do not retry by creating another customer or changing the original source identity.
After expiry or downgrade
Retained records may remain readable and exportable with the appropriate permissions. This does not authorize new premium writes. After expiry, permitted writes use the effective Free features and limits; they are still checked against current usage. An over-limit tenant must resolve capacity before adding more metered records.
Read access to retained data does not make every action available: editing, restoring, running automation and contacting a customer have their own checks. Contact archiving preserves history and still counts toward contact capacity. Ask an administrator to review the actual denial before removing data to make room.
See Customers, Deals, Activities, Reporting, Migration and connections and Configuration for each workflow.
Scope applies beyond navigation
The same boundaries apply to API/MCP tools, webhooks, migration approvals, restore and queued execution. Incoming integration data does not bypass capacity. Contact capacity counts net new canonical contacts rather than each channel alias; restoring a separate identity can consume capacity. Storage and provider API usage remain tenant-wide across companies.
Use the effective subscription usage/denial rather than a hardcoded plan table: add-ons, trials, expiry, legacy snapshots, explicit Enterprise contracts and release masks can change the available scope. Free access is limited, and Enterprise still has finite agreed capacity. See Native mobile navigation for the additional per-module data gates.