Open the admin console

Where the console is, what its sections do and how every request is checked.

In short

The admin console is where a site admin sets the rules the whole platform enforces: features, plans, limits, users and the platform's own settings. Only site admins see it, in the avatar menu.

Before you start

Open the console

  1. Open your avatar menu and choose "Admin console".
  2. The "Overview" opens with "Needs you". Its rows count unread support messages, open abuse cases, reports, billing matters, new failure reports and deployment settings to fix; each opens its section. When all is calm it reads "Nothing is waiting for you right now." Below come the tiles for People, Shared spaces, Plans given and Plans on offer. Plan distribution and Recent changes follow.
  3. Pick a plan in Plan distribution to open Users filtered to it, or pick another section in the list at the side.
  4. Type in "Find a section" to narrow the list; Enter opens the one left.

The list at the side starts with the Overview and "Platform dashboard", then groups the sections: People (Users, Organizations), Plans and money (Plans, Billing, Business, Feature access), Product (Activation, What's new, Help feedback, AI, Job sources), Safety (Abuse, Reports, Support inbox, Activity history) and Operations (Deployment, Data locations, Failure reports, Failure kinds and "Style guide"). "Platform dashboard" opens Analytics on Usage, and "Style guide" shows the product's look. A private installation adds License and Single sign-on and has no Data locations or Failure kinds. On a narrow screen the sections are tabs.

How access is decided

  1. Admin: on the console's own routes, a site admin is allowed what is not a customer feature. On every other route the role decides nothing.
  2. Feature policy: the feature's audience.
  3. Plan entitlement and limit: the feature is in the caller's plan and the metered limit is not used up.
  4. Resource permission: in an organization, the person's role is the ceiling, and the board, project or notebook's own preset and "Share" settings decide inside it. In a personal workspace, access goes to its owner and the people they shared it with by name.

Overview ends with this list, folded until you open it.

Good to know

The role opens the console, not organizations Everywhere outside the console the site-admin role decides nothing. Inside an organization a site admin is the member they are, or a stranger, and no private board, project or notebook opens for the role. Grant it sparingly, and use plans and feature rules for everyone else.

If something goes wrong

Related