Enterprise Workspace
Enterprise members, a dedicated login entry, the seat pool and enterprise audit — how to open and run the company-level management layer.
The enterprise workspace is a management layer stacked on top of ordinary accounts: it gathers your company's employee accounts, login entry, seats and audit trail under one owner. Personal and team usage stays exactly the same; the enterprise layer only answers who belongs to this company, how they sign in and how many seats that costs.
Opening one
- Open the enterprise console with the account that should own the enterprise; the page walks you through creating the workspace.
- Fill in the company name, the login short-link prefix and a uniform member-name prefix such as ACME.
- Once created, the current account becomes the enterprise owner and gains the four management areas: members, identity, audit and notifications.
There is exactly one enterprise owner, and everything in the console is scoped to this enterprise's members — data from other users or other enterprises never appears here.
The six areas of the console
| Pages | What it manages |
|---|---|
| Operations overview | Active member count, seat usage, the state of the identity entry and a roll-up of the last seven days of audit events. |
| Enterprise Member | Member status, enterprise login name, how they joined and their seat assignment; search by name, email or enterprise login name. |
| Teams and Seats | The owner's seat pool, what is taken and what remains, plus buying extra seats. |
| Identity and access | The enterprise's own login entry, the member login-name rules, and identity provider setup such as OIDC or SAML. |
| Enterprise Audit | Security and administrative events produced by this enterprise's members, graded routine / worth attention / high risk, exportable as CSV. |
| Enterprise notifications | Bulk email to this enterprise's members only; you must preview the recipient count before sending, and the history is kept. |
How members get in
Enterprise membership is not managed as a separate roster — it follows team invitations:
- Send an invitation to the employee's email from the team detail page — a seat is reserved the moment it goes out.
- When they accept, they gain both the team's privileges and enterprise membership.
- With zero seats available you cannot send new invitations until you buy more.
Seat capacity belongs to the enterprise owner and is shared across all of that owner's teams — one person in several teams still uses a single seat.
The enterprise's own login entry
The identity page can switch on a company-specific login path prefix without any DNS setup. Members who already accepted an invitation sign in through that link — but opening the link does not by itself add anyone to the enterprise. The entry is only an entry; membership still comes from the invitation.
The same page also sets the uniform prefix for member login names and connects your enterprise identity provider — OIDC, SAML or a self-hosted entry.
How it relates to teams and subscriptions
- Teams remain the day-to-day unit of collaboration: sharing workflows, sharing credentials and approving each other's work all happen at the team level.
- The enterprise layer governs boundary and identity: who counts as company staff, which entry they come through, how many seats they take and what audit trail they leave.
- Viewing the audit log is an Enterprise-plan capability; on other plans the platform records the events just the same, the viewer is simply not opened.
Next
- Teams — The concrete steps for creating a team and inviting members.
- Permissions & Sharing — The three-layer permission model: account role, team standing, workflow sharing.
- Subscriptions and Pricing — Seat billing and the capability comparison across plans.