Create a workspace
A workspace is the boundary everything in Metatate Cloud lives inside: its own catalog, policies, deployments, MCP tokens, members, and billing plan. Workspaces are fully isolated from each other, and each one has its own URL slug under app.getmetatate.com.
Sign upDirect link to Sign up
Go to app.getmetatate.com/sign-up and create an account with an email address and password, or continue with Google or GitHub.
Create your first workspaceDirect link to Create your first workspace
After signing in, use Create workspace from the workspace list. Pick a name; the workspace gets a slug that appears in every URL for that workspace. You become the workspace's owner, so you can complete the rest of the setup — loading sample data, connecting sources, and issuing MCP tokens — without further grants.
Invite teammatesDirect link to Invite teammates
Open Settings → Members to invite people by email and choose a role for each invitation; invitees join through the emailed invitation link. Admins can invite editors and viewers; only an owner can invite or promote another admin or owner. Member seats are limited by your plan — see plans.
RolesDirect link to Roles
Every member holds one of four roles, ordered viewer < editor < admin < owner. Each tier includes everything below it.
| Role | What it broadly can do |
|---|---|
| viewer | Read everything in the workspace. |
| editor | Author policies and submit them for review, curate the catalog (classifications, metadata, collections, scenarios, taxonomy), and create and publish deployment plans. |
| admin | Approve, reject, or archive policies, manage data sources and their credentials, issue and revoke MCP tokens, invite editors and viewers, and manage billing. |
| owner | Invite or promote admins and owners, change members' roles, remove members, and edit workspace settings. |
A fifth role, service_account, is reserved for a future machine-identity flow and cannot be granted to people.
Approval and publishing are deliberately split: editors can author policies and publish reviewed deployment plans, but approving a policy version takes an admin or owner. Plan your invitations so both halves of the review loop are covered.
Where to go nextDirect link to Where to go next
- Quick start — the fastest path to a first governed answer.
- Load the AcmeCloud sample — populate the new workspace with a safe, removable demo estate.
- Data sources overview — connect your own platforms instead.