Skip to content
Open the console

Admin & security

People, sign-in and directory sync for the whole workspace.

The Admin console is where a workspace’s owner and admins add and suspend people, decide how they sign in, and connect the company’s identity provider. Single sign-on and directory sync attach to a domain you have already verified for mail.

Owners and admins onlyTwo-step: an app or a passkeySSO by verified domain

An admin list of people with a sign-in status beside each name

People

Who is in the workspace, and what each person may do.

Add and suspend

Create accounts for your people. A suspended person loses access to mail within about half a minute, not at the next sign-in.

Import from a CSV

Every row is checked against the workspace and shown first; nothing is created until you press the button that says how many. Temporary passwords leave in one downloaded file, never on screen.

Custom roles that only narrow

A custom role is a subset of a person’s own role. It can take permissions away; it can never give anyone more than their role allows.

Single sign-on

Your people sign in with your identity provider.

Connect OpenID Connect or SAML 2.0 to a domain the workspace has verified in Domains. People with an address on that domain sign in through your provider, and an account is made for them the first time they do.

Require it, keep a way inOnly the owner can require single sign-on for a domain, and only with two-step of their own. Passwords are then refused for that domain — except an owner with two-step, so a provider outage does not lock the company out.
Verified domains onlyA domain that has not been verified for this workspace cannot be connected. Proving it once for mail is what makes it usable here.
Recorded before it changesEvery change to how a domain signs in is written to the audit log first. If the log cannot record it, nothing changes.
A plan view with one gate where every route meets

Directory sync

SCIM 2.0: your directory adds and removes people here.

A token per directory, shown once

Your identity provider calls with a SCIM token. Only its hash is kept, and you can revoke it from the console.

People and groups

Create, update, suspend and remove people from the directory. A suspension follows the same rule as one made by hand.

Groups change nothing until you map them

A directory group gains permissions only when an admin maps it to a custom role here.

Questions

Asked before the first domain is connected.

Who can open the Admin console?

The workspace’s owner and admins. Anyone else who opens it is told the workspace is managed by an admin.

Which identity providers work?

One that speaks OpenID Connect with a discovery document, or SAML 2.0. We have not yet run one for a customer in production, so we name none here.

What if our provider is down while single sign-on is required?

An owner who has two-step can still sign in with a password and the second step, and switch the requirement off.

Does directory sync give our identity provider admin powers?

No. A synced group changes what people may do only after an admin maps it to a custom role, and a custom role can only narrow.

Verify one domain. Turn on two-step. Connect a test provider.

Free to start, with no credit card.