Workspaces

Team management and access control

What is a workspace

A workspace is an isolated environment for your team. It contains your projects, integrations, API keys, and agent task history. Each workspace is a separate tenant — no data crosses workspace boundaries, and agent execution runs in isolated forked processes.

Workspaces map to WorkOS Organizations under the hood, which means they support enterprise features like SSO, directory sync, and audit logging out of the box.

Creating a workspace

To create a workspace, provide a name and a URL slug. The slug is used in workspace URLs and must be unique. The user who creates the workspace automatically becomes the owner with full administrative control.

After creating a workspace, the next steps are to connect your integrations (Linear, GitLab), add your Anthropic API key, and invite your team.

Roles

Workspace members have one of three roles that control their level of access:

RolePermissions
OwnerFull control. Can manage members, integrations, API keys, projects, and workspace settings. Can delete the workspace.
AdminCan manage members and invitations, configure integrations, and manage projects. Cannot delete the workspace.
MemberCan use agents, view activity and task history, and access projects. Cannot manage integrations or workspace settings.

Inviting members

Invite team members by email from the Members page in your workspace dashboard. Invitations are powered by WorkOS Organizations, which means they support SSO-ready onboarding.

Invited users receive an email with a link to join the workspace. If they already have a Ironwork account, they are added immediately. New users are guided through account creation first.

Membership changes are synced via WorkOS webhooks, so additions and removals from your identity provider are reflected automatically.

Switching workspaces

If you belong to multiple workspaces, use the workspace switcher in the dashboard sidebar to move between them. Each workspace has its own isolated set of projects, integrations, and agent history.