Organization read-only or without an active licence (license_read_only, license_inactive)

Symptom

• Administrative changes are refused with «The organization's licence has expired: it is read-only until the licence is renewed. Sign-in keeps working.» (API 403 license_read_only).
• Or: «No active licence allows this. Issue or renew the licence first.» (API 403 license_inactive), for example when issuing an activation code or allocating seats.
• The console shows a banner with «Licence details».

Cause

• The licence ended and the grace period (14 days by default) passed.
• The licence was revoked, or the organization never had one.
• The distributor's pool the licence comes from expired.

What keeps working

Sign-in, single sign-on and application sign-ins; ending sessions; changing a person's status (re-enabling needs a free seat); GDPR requests. Nothing is deleted.

Fix

• Administrator: ask your distributor or the platform to renew. See the details under «Manage» › «Licence».
• Distributor: renew your pool first if needed, then amend the customer licence's end date. Renewal ends read-only mode at once.

When to escalate

If the licence was renewed and read-only mode persists after a few minutes, contact the platform: the licence signature may be pending or have failed.