Appearance
Administration
How a workspace is run by the people who administer it: who may sign in, who may do what, how the workspace connects to the company's own identity provider, and what it may use.
Start here
- Authentication — sign-in links, passwords and two-step sign-in, OAuth, who may sign up, and how a link actually reaches somebody.
- Workspaces — starting one, renaming, moving and deleting it.
- Roles and permissions — the capabilities, and what each one lets a role do.
People and places
- Groups — named sets of people, for grants that apply to a team rather than to each member.
- Single sign-on — the workspace's own identity provider: domains proven by DNS, roles from the provider's groups, members synced over SCIM, and sign-in rules such as "two-step for everyone".
- API keys — service identities for work that outlives a person.
- Webhooks — a URL that is told when things happen, and a daily digest.
- Assistant — which models it may use, where the workspace's writing goes, and what it may do without asking.
Operating it
- Packages, quotas and the audit log — what a workspace may use, and the record of who changed what.
- Billing and invoices — what a workspace pays for, and what its customers see.
The two consoles
The difference between them is the whole design, so it is worth understanding before you give anybody either one.
A workspace admin runs their own workspace: members, invitations, groups, roles, keys, webhooks, SSO, sites, its own settings and its audit log. That lives in the Workspace tab of Settings, inside the app, because administering a workspace is something you do while working in it.
An operator runs the platform: which workspaces exist, how big they are, the quotas each may not exceed, suspending, renaming, moving and deleting them, who may start one, who may sign up, and accounts. That is a console of its own, and it offers no way to open a page. The absence is the feature — a console that quietly listed page titles would break the tenant boundary without anybody choosing to break it.
An operator who genuinely needs to look inside a workspace uses break-glass, says why in a sentence somebody else will read, and the workspace's own admins see the entry in their log.