Workspaces, teams, roles and API keys

Everything in WECOMMANDER belongs to a workspace: devices, approvals, scheduled tasks, the audit log and the plan. You can belong to several workspaces and switch between them; create a new one from Account.

Roles

RoleCan
ViewerSee devices and read with read-only tools; use servers shared in the team library without changing them.
OperatorRun tools on devices; high-risk actions still need an approval. Gives the team key to new members' apps.
AdminApprove and deny, manage members, devices, AI permissions, allowed commands, autonomous mode and scheduled tasks.
OwnerEverything, including billing and the region. A workspace always keeps at least one owner.

Admins cannot grant a role above their own. Changing a role or removing a member takes effect at once; a removed member's browser sessions for that workspace end.

Inviting members

  1. Administration → Team → Invite: enter the e-mail address and choose the role.
  2. Copy the invitation link and send it through a channel you trust. It is valid for 72 hours and only once.
  3. The person creates an account with the link or joins with their existing account (they confirm with their current password).

Pending invitations count toward the plan's member limit; you can revoke one before it is used.

API access keys

For MCP clients and scripts that use a bearer token instead of OAuth: AI → MCP tools → create an access key with a name and a role. The key is shown only once; store it safely and revoke it when no longer needed. Use the lowest role that works. Keys cannot approve actions or change AI permissions.

Region

Owners can choose a preferred region for the workspace on the Team page, or leave it on automatic. Devices move to the new region on their next connection; if the region is unavailable, WECOMMANDER falls back to another healthy one without re-pairing.