Workspaces, members and roles
A workspace is the container everything in Elva belongs to: your collections, contracts, MCP servers, integrations, webhooks, and billing. Every collection lives in exactly one workspace, and permissions are decided at the workspace level rather than per resource.
You can belong to several, one per team or one per client, and switch between them from the workspace switcher at the bottom of the sidebar.
Two roles
Elva keeps the permission model deliberately small. There are two roles, and the line between them is the line between doing the work and changing what the workspace is.
Editor
The day-to-day work: create and edit collections, edit MCP servers, and use the MCP Playground.
Admin
Everything an editor can do, plus the shape of the workspace itself: members, roles, billing, webhooks, and contracts.
In practice that means an admin is the only role that can invite or remove members, change someone's role, manage the plan and billing, configure webhooks, and create, publish or delete API contracts. Deleting the workspace is admin-only too. Everything else an engineer does day to day sits with editor, so you rarely need to hand out admin just to unblock someone.
Approving a contract is not an admin action. An approver is usually a reviewer rather than a workspace administrator, so approval is checked against the contract's own assigned approvers instead of the workspace role. You do not have to promote someone to admin just to let them sign off.
Inviting people
Admins invite by email from workspace settings, choosing the role at the same time. An invitation can be resent if it was missed, or revoked before it is accepted. The recipient follows the link, signs in or signs up, and joins with the role you picked.
From the members list an admin can change any member's role or remove them. To step away from a workspace yourself, use the leave option rather than removing your own membership.
Where to go next
On this page
- Workspaces, members and roles