Application administrator

An account carrying the app admin capability runs the application's identity: who the accounts are, the roles they can hold, the policies they sign in under, and how the gateway's own pages look. It does not decide where requests go - that is the infrastructure administrator.

The capability is a flag on the account, set from Application > Users by another application administrator or root. See Administration capabilities.

The console of an application administrator: Application, Vault, Data plane and Meerkat in the rail, the Application menu open on Users

What you see

The console opens on Application > General. The rail holds four entries: Application, Vault, Data plane and Meerkat.

Section Screens
Application General, Roles, Users, Built-in pages, Portal, Security, Access tokens - and Plug while the developer tunnel is open
Vault the entries of the application
Data plane Audit, Sessions, Scheduler, Notifications, Issues
Meerkat Audit, API reference, Release notes, License

On an installation with a single tenant, its Groups, Members and Group rules are in the Application menu too: there is one tenant, and nobody has to choose it. With several, they are each tenant's, under Tenants.

What you do there

What is not yours

You do not see It belongs to
Routes, authorities, TLS, the mail relay, the model, metrics, logs the infrastructure administrator
A tenant's own screens, on an installation with several the tenant's administrators
Configuration (export, import, backup) and the console's own sessions root

A screen you may not open sends you back to General, even typed into the address bar, and the admin API answers 403 on its calls.