Team policies, plans and seats

Read the server's plan and policy state rather than embedding a price table or assuming that a role implies a paid feature. The public billing endpoint is a read. Purchases and seat changes happen in the Handwrite Billing tab with billing authority.

Capacity and entitlement

Roles have separate seat allowances. Adding, inviting, accepting and changing a role perform seat checks; live pending invitations reserve seats. A team has a hard maximum of 500 members, and a person can belong to at most 100 organisations. Expect 402 seats_exhausted when a role has no capacity and 422 limit_reached at a hard limit. Do not silently move a user into a different role to bypass a capacity failure.

Policies, managed tokens, usage, insights and live editing depend on plan features. SSO is a Team Plus capability in current source. Org-owned credentials and org webhooks require the developer feature in the current implementation. The source plan catalogue is not evidence of a completed purchase or deployed portal.

Stored rules versus effective policy

Rules use {value, locked}. Within one organisation, a stored member override replaces that organisation's rule for the same key, including its lock; forced minors safeguards apply afterward. Across applicable organisations, stricter values win and locks are combined. The smaller non-zero numeric limit is stricter; zero means no additional policy limit. A stored policy field is not proof that every request path enforces it.

The table below describes applicable member-credential policy. Org-owned tokens have a separate authentication path; see the enforcement limits in credentials.

Control	App implication
apiAccess = on	Personal API credentials can be used subject to other checks.
apiAccess = managed	Use a token managed by an applicable organisation; an unmanaged key or OAuth grant can be refused.
apiAccess = off	API keys/OAuth are refused, including admin accounts under current source enforcement.
thirdPartyApps	Governs third-party OAuth use separately from API-key policy.
sharingOutsideOrg / publicLinks	Hide unsupported sharing choices and still handle server refusals.
cloudVoices / audioMonthlyCharacters	Cloud speech may be disabled or capped; show quota failures clearly.
dailyRequests	Stored and returned, but not currently enforced by the public request counter. The wrapper uses the global daily cap, not this organisation policy value.
liveEditing	Admission to collaborative editing may be refused even with document access.
developerAccess	Org-only control over org-token creators; not a member override.
usageVisibility	Governs which counters other team roles can see.

Use GET /api/v1/orgs/{id}/policies for the team's stored/default/effective view, a member-policy read for that member's override, and /api/v1/me/policy for the connected person's combined effective policy. Respect returned locked settings in the app; retrying a blocked write does not unlock it.

PUT replaces a complete stored map. Show a review of the intended replacement and retain unchanged rules. Clearing a member override restores other applicable rules rather than granting unrestricted access. Current source includes staff-origin API suspension for the member-credential path: it is displayed as a staff restriction and cannot be lifted by editing team rules. The new org-owned token path omits that common gate, so staff suspension alone is not proof those tokens have stopped. This control's release was not verified in this documentation task.

Source: org-plans.ts, seats.ts, org-policy-keys.ts, policies.ts, policy-views.ts and staff-controls.ts.

Team policies, plans and seats

Capacity and entitlement#

Stored rules versus effective policy#

Capacity and entitlement

Stored rules versus effective policy