Subscription, seats, storage and AI
Billing is managed at the organization level. It combines the subscription state, active paid seats, stored artefacts and the optional AI tier; no project has a separate subscription.
Access and status
UI path: top navigation → Administration
Only an organization Owner or Admin can open the administration dashboard and storage controls. When the organization uses self-service billing, the Subscription card shows the plan name, provider status and Renews: date. Managed or non-Stripe organizations may not show this card; contact the account administrator rather than assuming there is no entitlement.
Common provider states include trialing, active, past_due, unpaid, incomplete_expired and canceled. Trialing/active subscriptions permit normal work. An inactive or failed paid subscription keeps existing projects viewable but blocks new PDF uploads and project exports. This boundary protects existing work while the billing issue is corrected.
Subscription lifecycle
To stop renewal, select Cancel subscription and confirm. The card then shows Ends at the period end — will not renew. Access continues to the displayed period end. Select Resume subscription before that date to clear the scheduled cancellation.
A cancellation is not immediate data deletion. Projects remain subject to the organization's retention and deletion controls. If a cancel/resume request reports an error, reload the card before retrying: the visible ending state and period date are the result to trust. Do not repeat the action rapidly or attempt to change billing through project settings. See Organization administration and Security, privacy and Law 25.
Seats
A paid seat is an active member whose organization role is Owner, Admin, Project manager or Editor. Active Viewers are not counted as paid seats. Project-specific Viewer/Reviewer/Editor/Project admin access does not by itself change the organization seat category.
UI path: Administration → Users
Role changes, reactivation, deactivation and deletion recalculate seats. If an increase or role change cannot synchronize with billing, PlanRelevé reports Stripe seat update failed — the change was not applied. Reload Users and verify the old role remains. Deactivation revokes the member's current session and lowers the active count; never deactivate the last Owner/Admin. For invitation and role procedures, see Members, roles and invitations.
Storage usage
UI path: Administration → Storage
The page shows Used, Included and Overage, then breaks usage down by artefact type. Included capacity is the organization's base storage plus purchased extra storage. Source PDFs and encrypted generated/attached artefacts contribute to usage. If usage exceeds included capacity, metered overage is rounded up to whole GB against the monthly peak; removing an item later does not make an already-recorded peak disappear.
If purchasing is available, Buy extra storage offers the capacity increments displayed in the selector and sends the administrator to the configured checkout. This article intentionally does not quote prices: use the current plan/checkout display or your agreement. A successful payment must be confirmed before extra capacity appears. Return to Storage and verify Included changed; if it did not, do not upload duplicates—contact billing support with the checkout time and organization name, not card details.
Retention settings do not instantly reduce Used. Exports (days, empty = keep) and Renders (days, empty = keep) store the cleanup policy for those generated artefacts; source plans are outside these two fields.
AI tier and consent
The administration AI card shows Included (1×), AI 5× or AI 20×, plus monthly input/output percentages. Availability first depends on the organization's plan. A self-service upgrade applies immediately; a downgrade to a lower tier or Included is scheduled for the paid period end, where Undo change can reverse it beforehand.
Tier and consent are different controls. Enable AI features is required, and Allow AI on plan/spec content is a second consent before document content may be used. Paying for a tier does not turn on either consent, and disabling consent does not itself cancel the tier. See AI assistant and approved actions and API and MCP integrations.