Admin console

Your node ships with an admin console so you can administer your own federated server. It runs on your box, against your database, and it is one of the web surfaces the node serves under your own domain.

It is the admin surface. By default it answers at admin. in front of your home server — a node whose home server is police.org serves the console at https://admin.police.org. If you set a different admin host in your configuration, that is where it is.

The admin surface is the recovery surface. Every other surface — the personal portal, the business portal, the verification page, the provider portal, the status page — can be stopped and started with tc-operator service. The admin surface cannot be stopped that way.

Who May Sign In

Only an account that holds the operator_admin role on this node. Anyone else who signs in successfully is rejected and signed straight back out; the login screen tells them the account is not an admin on this environment.

Your first admin is created for you at install. See Signing in.

What It Administers

This server, and nothing else. Your users, their sessions and login history, blocked sign-in attempts, your organisations, your vaults, your notification templates and delivery queues, your audit and function logs, and the settings that decide who may connect here.

It does not administer the plans your node runs under. The entitlement ceiling is granted and signed centrally, and you administer your members inside it — the console has no screen that raises it, and the server refuses any attempt even when a control is on screen. See Roles and permissions.

The Sections

Signing in — the first admin, the sign-in methods your node offers, and adding more administrators.

Roles and permissions — what operator_admin may do, the two extra permissions, and the controls that will refuse you.

People and vaults — Users, Sessions, Login History, Blocked Attempts, Organizations and Vaults.

This server — Surfaces, Node Settings, who may connect here, and the connection activity log.

Notifications and logs — templates, delivery queues, the audit log, function logs, and the Dashboard.