Skip to main content
Workspace members are the people from your organization who can open a given workspace. Each one has a workspace role (Admin, Developer, or Viewer) that decides what they can do there.

​
How workspace access works

A person must belong to the organization before you can add them to a workspace. Their organization role sets their default access: A per-workspace role is called a role override. Use it to let a Viewer run work in one sandbox workspace, or to make a Developer the Admin of their team’s workspace without giving them organization-wide control.
Workspace Admin can add, edit, and remove connections and credentials, and manage approvals. Grant it sparingly on workspaces connected to production.

​
Prerequisites

  • You’re a workspace Admin (organization Owners and Admins always are).
  • The person is already in the organization. To invite someone new, see invite members.

​
Add members from the workspace

1

Open the Members tab

In the sidebar, click More → Workspace settings and select Members. The Chat Settings icon in the chat box opens the same dialog.
2

Start adding

Click Add Member. The Add people to <workspace> dialog lists organization Developers and Viewers who aren’t in this workspace yet. Owners and Admins aren’t listed because they already have access.
3

Pick people and a role

Select one or more people. With one person selected, you can change Joins as to override their role. With two or more, everyone joins with their organization role. To give some of them a different role, add them, then change each Workspace Role in the members table.
4

Add

Click Add to confirm (the button shows how many people you’re adding).Success state: each person appears in the members table with their Organization Role and Workspace Role.

​
Set access across workspaces at once

Use this when one person needs access to several workspaces. You need to be an organization Owner or Admin. A workspace Admin through an override can’t open this screen.
1

Find the member

Go to Admin Settings → Organization and find them in Members.
2

Open their workspace access

Click Edit Workspace Access on their row. This option shows for Developers and Viewers only.
3

Choose workspaces and roles

Check each workspace they should open. For each one, keep Inherit from Org or pick Admin, Developer, or Viewer.
4

Save

Click Save.Success state: the workspaces appear in their account menu the next time they open it.

​
Workspace roles

Viewers are read-only: they can open conversations, findings, and dashboards, but can’t send chat messages or run commands. The one change a Viewer can make is installing a Skills Hub skill into the workspace. Developers do day-to-day work. Admins also configure the workspace. *Developers can’t change incidents in Resolve. To let an on-call engineer work incidents in one workspace, make them workspace Admin there. Who can approve an agent’s action is set separately. See approvers. Some controls sit above workspace roles. Admin Settings, usage, and audit logs are for organization Owners and Admins. The one exception is the Guardrails page: Admin Settings isn’t in a workspace Admin’s menu, but they can open Guardrails from a direct link to manage their workspace’s rules. Billing and organization-wide BYOK are Owner-only.

​
Change a role or remove someone

Open More → Workspace settings → Members. The table shows Member, Organization Role, Workspace Role, and Actions. Organization Owners and Admins show a fixed role with no remove option, since their access comes from the organization. Removing someone from a workspace keeps them in the organization, so you can add them back later. Automations they own in this workspace turn off. A workspace Admin clicks Take ownership on each one, then turns it back on. To remove someone from every workspace at once, remove them from the organization in Admin Settings → Organization.

​
Add members automatically with SSO

You need to be the organization Owner to change these provisioning settings. If you use SSO with just-in-time provisioning or SCIM, new members can join workspaces as soon as they’re created. Go to Admin Settings → Identity and access and set Auto-assigned workspaces on the Provisioning & directory sync card. New members join those workspaces with their Auto-assigned organization role (Viewer by default). See SSO and SCIM group mapping.

​
Troubleshooting

Cause: they’re not in the organization yet, they’re already in this workspace, or they’re an organization Owner or Admin (who already has access).Fix: check the members table first. If they’re missing from the organization, invite them.
Cause: they’re an organization Owner or Admin, or you aren’t a workspace Admin.Fix: change their organization role in Admin Settings → Organization, or ask a workspace Admin.
Cause: Viewers are read-only and can’t send chat messages.Fix: change their Workspace Role to Developer for this workspace, or change their organization role in Admin Settings → Organization to apply it everywhere.
Cause: you aren’t a workspace Admin.Fix: ask an Admin of this workspace, or an organization Owner or Admin, to add the person.

​
Next steps

Set up approvals

Decide which agent actions need a person to approve them.

Roles and permissions

See every organization and workspace permission in one place.