Administration

Run your tenant, team and security

The settings that are boring right up until they are not: who has access, how they sign in, what you are paying for, and what happens to your data when somebody asks.

Very little of this is daily work. Most of it is a handful of decisions made once and reviewed quarterly. That is why it gets skipped, and why the failures are so predictable. A colleague who left in March still has a session in September. A card expired between renewals and the invoice failed silently. Somebody sends an Auskunftsersuchen with a 30-day clock and nobody knows who answers it.

Cockpit screens: partly planned. Team, sign-in, apps, billing and the security settings on these pages are shipped. Four things are not yet on your tenant: a role editor for Cockpit colleagues, a self-service setup for federating your own directory (Entra ID, Active Directory), notification rules, and an audit-log export. Where a page touches one of them, it says so and describes what you do in the meantime.
Start here.Tenants, apps and markets explains the four words the rest of this area uses constantly. It also draws the line between your team and your customers' buyers: two separate sets of people, confused often enough to be worth twenty minutes.

Understand

  • Tenants, apps and markets — what a tenant is, why everything is an app, what your subscription includes, and where markets fit.

Set up

Your team and your platform's shape.

  • Users, roles and permissions — invite colleagues, suspend and remove them, and what roles can and cannot do today.
  • Single sign-on — how sign-in works, what the failure page means, and connecting your own directory.
  • Apps and the Marketplace — installing, approving an update that asks for more access, and what uninstalling does not delete.

Work with it

Keep it healthy