The Admin console provides server-wide views of every user and organisation on the instance. These pages display personally identifiable information (names, email addresses) — handle that data in accordance with your privacy policy and applicable regulations.
The Users page lists every registered account on the server and requires the User List global permission. For each user it shows their name, email, language, account creation date, last login, and the global permissions they hold.
The list is paginated and can be sorted by name, email, creation date, or last login.
Administrators with the User Edit global permission can change a user's global permissions:
You can only grant permissions you hold yourself — any permission you lack is disabled in the editor, so you cannot escalate another account beyond your own access.
Accounts can be deactivated (blocked) and later reactivated by callers with the User Edit permission. A deactivated user cannot log in. These actions are available through the user administration API (/v1/user/deactivate and /v1/user/reactivate).
If New users created as disabled is enabled in Server Configuration, newly registered accounts start deactivated and must be reactivated before they can be used.
The Organisations page lists every organisation registered on the server and requires the Org List global permission. Organisations pending deletion are excluded from the list.
Each organisation is shown with its name, member count, project count, and the owner's name and email. This gives administrators a server-wide view of how the instance is being used without needing to be a member of each organisation.
Day-to-day organisation management — members, roles, settings, and ownership — is performed by the organisation's own members from within the organisation. See the user guide's Organisations page for those workflows.
For the underlying APIs, see /_user/list and the Users (v1) endpoints and /_org/listall in the developer guide.