Admin
Admin (?tab=admin) sits at the top of the rail footer. The rail draws it only when the server
says you administer the instance in focus (drilled into from the Overview’s bird’s-eye), and the
page itself refuses to read anything for anyone else. Without an instance in focus it says:
“Choose an instance first: the Admin page manages the members and seats of one instance.”
An admin is a spec.users entry with role admin on that instance’s live ClientInstance (expiry
honoured), or the installation’s TIDE_PLATFORM_ADMIN.
Sections
| Section | What it does |
|---|---|
| Members | who may use the instance, and with which role (admin, writer or reader) |
| Seats | the seats of the instance’s subscription. Without a payment provider it says billing is not connected. |
| Carrier: WhatsApp, SMS and calls | the contacts an audit may be sent to, and the carrier this instance sends through. Platform console only. |
| Platform settings | the installation’s GitHub organisation and the repositories the agents work in, which agent features are switched on, and the cloud providers. Platform console only. Saving is refused unless the console lists you as an admin of that setting. |
How a member change lands
A change patches the whole spec.users list of the ClientInstance, carrying its
resourceVersion, so a raced change is refused rather than silently undone. It shows PENDING
until the operator re-projects the application’s users and the application rolls. Nobody changes
their own access, and the last admin stays.