Subscription, seats, storage and AI
Billing is managed at the organization level; no project has a separate subscription. The administration page summarizes the subscription, active seats, storage and AI tier. Amounts and terms can vary by organization; rely on the agreement and the current screen rather than a price copied into this wiki.
Access and status
UI path: account menu (your initial, top right) → Administration, the Organization administration page. Only an organization Owner or Admin can see this information and the storage controls.
The Subscription card appears for a self-service billed organization when a subscription exists. It shows the plan name, its status, the Renews: date and, when applicable, Ends at the period end — will not renew. If the organization is internal or manually billed, the card and self-service buttons may be absent; contact the account administrator rather than assuming there is no entitlement.
The status is shown as the payment provider reports it, for example trialing, active, past_due, unpaid, incomplete_expired or canceled. active and trialing permit new uploads and exports. An inactive, failed or ended subscription blocks both actions, but authorized members can still view existing projects.
Subscription lifecycle
- Check the status and period date before a change.
- Select Cancel subscription, then confirm: the end is scheduled for the period date and access continues until then.
- Resume subscription clears that scheduled end as long as the date has not passed.
- After the end, do not start a new upload or promise an export until reactivation is confirmed.
A cancellation is not data deletion: projects remain subject to the organization's retention and deletion controls. If a request returns a payment-provider error, reload the page before retrying; the displayed state and date are the result to trust. Do not repeat changes rapidly, do not try to change billing from a project and never send card numbers or secrets to PlanRelevé support. See Organization administration and Security, privacy and Law 25.
Seats
The counter uses the organization role of active accounts:
- Owner, Admin, Project manager and Editor count as active seats;
- Viewer is a free seat: it is not a billable seat and can only be given the Viewer role on a project;
- a deactivated account does not count;
- a one-off project share does not by itself change the organization role this counter uses.
UI path: Administration → Users. A role change, reactivation, deactivation or deletion recalculates seats. If an increase or role change cannot synchronize with billing, PlanRelevé shows Stripe seat update failed — the change was not applied. and the old role remains. Check Users before retrying. Deactivation revokes the member's session and lowers the count; the last active owner cannot be deactivated. See Members, roles and invitations.
Storage usage
UI path: Administration → Storage.
The page shows Used, Included and Overage, with a breakdown by artefact type. Included capacity is the base storage plus any purchased extra storage. Source PDFs and encrypted generated or attached artefacts count toward usage. Overage is rounded up to the next GB. For a metered organization, monthly billing takes the usage peak above included capacity and sends only growth not yet counted in the period; removing an item later does not erase an already-recorded peak.
If purchasing is available, Buy extra storage offers the increments shown in the selector and sends the administrator to the configured checkout. This article intentionally quotes no prices: rely on the checkout screen or your agreement. Payment must be confirmed before the capacity appears. Return to Storage and verify that Included changed; if it did not, do not upload duplicates and contact billing support with the checkout time and organization name, never card details.
Before adding storage, archive what should be archived and review the retention policy. A project archive is still stored data; it is not a deletion. Retention does not lower Used on the spot: Exports (days, empty = keep) covers only organization data exports, deleted by a daily job, and source plans do not depend on it. See Organization administration for that field and Security, privacy and Law 25 for data export or deletion.
AI tier and consent
The Artificial intelligence card distinguishes Included (1×), AI 5× and AI 20×. The Included (1×) tier is provided to every organization, whatever its plan; the other two multiply the monthly quota. The Input and Output bars show percentages, not raw tokens. An assistant message that carries an image counts 5× against this quota, input and output alike.
- A self-service upgrade applies immediately and replaces any pending change.
- A downgrade, to a lower tier or Included (1×), is scheduled for the paid period end; Undo change keeps the current tier.
- These changes require an active Stripe subscription; otherwise the interface shows An active Stripe subscription is required to upgrade.
- At the monthly limit, AI features wait for the next month or a higher tier.
- The tier does not replace the two organization consents: Enable AI features and, separately, Allow AI on plan/spec content. Paying for a tier turns on neither consent, and withdrawing a consent does not cancel the tier.
If a consent is missing, the interface says so without enabling the feature. See AI assistant and approved actions and API and MCP integrations.
Quick recovery
- Upload/export blocked: check the subscription status first, then your project role.
- Role unchanged: the seat-synchronization message means the old role was kept.
- Unexpected storage: open the per-artefact breakdown; archiving alone frees no space.
- AI downgrade missing: look for the "Changes to … on …" notice and the Undo change button.
- Subscription card missing: the organization may be manually billed; contact the account manager rather than assuming an outage.