Skip to content

Workspaces and roles

A workspace is your company in Orqane. It holds your teams, employees, connectors, knowledge bases, wallets, policies and billing. Humans who access it are members, and each member has one role.

Object Scope
Teams and employees Every employee belongs to exactly one workspace and one team.
Connectors and MCP servers Authenticated once for the workspace, then granted to employees.
Knowledge bases Shared at workspace, team or employee scope.
Treasury and wallets One treasury per workspace funds every employee wallet.
Policies and guardrails Apply to every employee in the workspace.
Billing One plan, one credit balance and one invoice per workspace.

Data never crosses workspaces. An employee in one workspace can’t read the memory, knowledge or records of another, even if the same person is a member of both. To work with agents outside your workspace, use A2A or MCP.

When you create a workspace, you choose where its data is stored and processed:

Region Location Use it when
EU European Union Your data must stay in the EU, for example under GDPR or customer contracts.
US United States Your company and customers are mainly in North America.

Memory, knowledge bases, run history, files and the audit log stay in the region you choose. Model calls are routed to providers in the same region when one is available. See Models for the details per model.

Each member has one role. Roles are cumulative: each role can do everything the role below it can do.

Role What they can do
Owner Everything an Admin can do, plus manage the plan and payment method, transfer ownership and delete the workspace. Each workspace has exactly one Owner.
Admin Invite and remove members, change roles, configure SSO, connectors, policies and guardrails, fund wallets from the treasury, grant L4 Delegate, and see the full audit log.
Builder Create and edit employees, skills, teams and knowledge bases, connect MCP servers, hire from and publish to the marketplace. Builders can’t change policies or move money.
Manager Act as human manager of employees: answer their approvals, assign tasks, take over runs, change autonomy levels up to L3, and run performance reviews.
Viewer Read employee profiles, activity, costs and reports. Viewers can chat with employees that allow it, but can’t approve anything.

A member can be the human manager of an employee only if they have the Manager role or above. For the full list of permissions per role, see Permissions.

Open member settings

Go to Settings > Members and click Invite.

Enter emails and a role

Enter one or more email addresses, separated by commas, and choose a role. You can also add the new members to one or more teams.

Send the invitations

Click Send invitations. Each person receives an email with a link that is valid for 7 days. Pending invitations appear in the Invitations list, where you can resend or revoke them.

Only Admins and the Owner can invite members. To let people join without an invitation, add your company’s email domain under Settings > Members > Allowed domains. Anyone with a verified address at that domain can join as a Viewer.

Open Settings > Members, then click the member’s name.

  • To change their role, select a new one in Role. The change takes effect immediately.
  • To remove them, click Remove from workspace. Their pending approvals are reassigned to the next person in the escalation chain.

If you remove the human manager of an employee, Orqane asks you to choose a new one before it completes the removal. An employee always has a human manager.

On the Business and Enterprise plans, Admins can require sign-in through your identity provider with SAML 2.0 or OpenID Connect. Okta, Microsoft Entra ID and Google Workspace are supported. With SCIM provisioning, members are created, updated and removed automatically, and you can map identity provider groups to Orqane roles. See Security to set it up.