Subscription administrators

01In a nutshell #sec_8543fd38

This page governs the entire subscription: one person — never a group — with an authorization that expires within twelve months and is explicitly re-granted, so that the list purges itself.

02Where #sec_78cc26b8

Security & access › Administrators. At the top, Subscription authorizations, and the border with the other screen: rights within a workspace are set elsewhere — the Workspace roles link leads there, and the roles page explains it.

03What an administrator is #sec_f48b0e21

The screen defines it: one person — never a group — who governs this subscription: workspaces, authorizations, settings. The role is unique and closed: there is nothing to compose.

There is therefore no "read-only" administrator, no "billing only" administrator. Someone is a subscription administrator, or is not. What this opens is everything that this journey describes.

Where the first one comes from. The first administrator is designated by REVIEWIT at the opening of the service. All the following are granted here.

04Granting an authorization #sec_12918064

Granting an authorization opens the panel. The eligibility rule is written on the empty screen, and it always applies: the holder must exist in a directory that opens a REVIEWIT session, and this directory must have been collected. They do NOT need to have logged in: the authorization is placed on the person, their account is born from their first session.

Then a deadline — twelve months at most — and a reason. The reason is displayed in the list; write it for the one who will read the list in six months.

05Reading the list #sec_56c20f26

Four counters at the top: active, expired, suspended, revoked. Then one line per authorization: holder, active status, granted on / by, expiration (in N months, in N days, no longer confers anything, frozen), reason.

Two marks to know. (you) — it's your own line. Last active administrator — this person is the only one who still governs; revoking them or letting them expire without granting another would leave the subscription without an administrator.

06"N things require your attention" #sec_ffb9cbb6

The alert block at the top names what is urgent:

• … has expired — their authorization no longer confers anything, even if displayed as active in the database.
• *N expirations fall within 30 days. An authorization does not extend: it is

re-granted.*

This last point is the entire doctrine. There is no "extend" button. There is Move expiration for a date correction, and otherwise, at expiration, a new grant — traced, motivated, dated.

07Suspend, reactivate, revoke #sec_a31217b8

On one line: Suspend (the authorization is frozen, it no longer confers anything, it can return), Reactivate, Revoke (definitive, traced). Detail opens the authorization history.

Suspending during a long absence is a good practice, not an excessive precaution: a subscription administrator who does not look at their console for three months is an open access that no one is monitoring.

08Why the list remains short #sec_3857e9de

The screen explains it: each authorization expires within 12 months at most and is explicitly re-granted. Nothing renews silently — the list purges itself.

It's the same rule that REVIEWIT enforces on your resources. A subscription whose administrator list includes ten names, six of which have expired, does not have a product problem; it has six people whose continued presence has not been verified by anyone.

09The rhythm #sec_9fd7f42a

10To remember #sec_435622ce

One person, one reason, an end date, and nothing that renews itself. The short list is a sign that the rule is applied. And always keep a second effective administrator: the day the last one leaves, the subscription no longer has anyone to appoint another.