Workspaces and team access

Select a workspace

Use the workspace menu in Atrium to choose where you are working. Installed apps, team membership, and publisher resources belong to workspaces. Check this selection before installing an app, reviewing pricing, or editing a Studio listing.

Changing the browser's workspace does not automatically change an existing CLI token. Verify API context separately when a resource appears missing or access is denied.

Invite collaborators

An authorized administrator can use Settings > Team to invite members by email and select an available role. The recipient follows the invitation link and signs in with the invited account.

The Team page provides controls for pending invitations, including Resend Invite and Annul Invite, and for managing existing members. Annul an invitation when its link should no longer grant access. Review role changes and removals before confirming them.

Available controls and successful actions depend on authorization. Do not infer a complete permission matrix from a role's name or from a visible menu; verify the operation with the intended role. App launch and subscription-management permissions can differ.

If an invitation fails, check the invited email, signed-in account, selected workspace, and whether the invitation was revoked or already accepted. Ask an authorized administrator to resend it when needed.

API and CLI workspace context

Use a developer access token to inspect its context:

GET /v0/platform/me
Authorization: Bearer <access-token>

List memberships and select a workspace through the API:

GET /v0/platform/workspaces
Authorization: Bearer <access-token>

POST /v0/platform/workspaces/<workspace-id>/select
Authorization: Bearer <access-token>

For CLI authentication, selection returns a fresh access token. Use that token for subsequent requests; continuing with the old token can leave requests scoped to the previous workspace.

Stable CLI 0.1.16 has no workspace subcommand. Use the browser for browser workspace selection and the API for custom client selection. Do not rely on commands shown only in an unreleased build. See Authentication for token handling.

Keep customer data scoped

Publisher access to an app does not grant access to every customer's records. Enforce user and workspace authorization in your app and database queries, including case lists and mutations.

Test with two workspaces and at least one non-owner account. Verify that switching scope cannot expose the other workspace's cases, installation management, or developer resources.