Workspace Members

A workspace is your team’s dedicated environment on the Agent Platform. It enforces isolated data boundaries, controls which AI models and features are available, and determines what each team member can do.

Within a workspace, projects let you group related agents and resources by use case. And if your company runs multiple teams, an optional organization layer ties workspaces together under shared billing and governance.

Understanding this structure upfront makes onboarding, role assignment, and day-to-day administration significantly easier.

Resource Hierarchy

The Agent Platform organizes resources across three levels. You don’t need all three - start with a workspace, add projects as your work grows, and only set up an organization if you need to manage multiple workspaces together.

• Workspace - Your team’s dedicated environment. Contains all agents, models, connectors, secrets, and members.
• Project - A group of related agents and resources for a specific use case, sitting inside a workspace.
• Organization - An optional layer above workspaces for shared billing and governance across multiple teams.

Workspace

A workspace is the foundation. Everything you create - agents, models, connectors, secrets, guardrails - lives inside one. Each workspace is completely isolated, so data in one workspace is never accessible from another.

Key behaviors:

Who has access and what they can do (team membership and roles) Which AI models and providers are available (LLM policies, token budgets, rate limits) Which features are unlocked (based on your plan tier)

Project

A project sits inside a workspace and groups related agents, knowledge bases, tools, and environment variables for a specific use case. A workspace can have many projects.

For example, a workspace shared by a platform team might have separate projects for a customer support agent, an internal HR assistant, and a data pipeline agent - each with its own members, environment variables, and secrets.

Key behaviors:

Projects inherit the workspace’s AI model configuration but can override model tier assignments. Project members are drawn from workspace members, with their own project-specific roles. Environment variables and secrets can be scoped per project and per environment (development, staging, production).

Organization

An organization is optional and sits above workspaces. It exists purely for billing and governance - use it when multiple teams each have their own workspace but need to share a single billing account, credit pool, or security policy.

A single-workspace setup doesn’t need an organization.

Workspace Roles and Permissions

The Agent Platform uses hierarchical role-based access control (RBAC). Each role inherits all permissions from the roles below it.

Workspace Roles

These roles apply across the entire workspace:

Role	Description	Key Permissions
Owner	Full control over the workspace. One owner per workspace.	Transfer ownership, delete workspace, manage billing, all admin operations
Admin	Manages team members, models, and workspace settings.	Invite/remove members, configure models, manage secrets and connectors, view audit logs
Operator	Manages agent deployments and monitors production.	Deploy agents, view analytics, manage environment variables, and view sessions
Member	Builds and tests agents within assigned projects.	Create/edit agents, run tests, and manage project-level resources
Viewer	Read-only access to workspace resources.	View agents, view project configurations, view analytics dashboards

Project Roles

Projects have their own role assignments that further restrict or specialize access within that project:

Role	Description	Key Permissions
Admin	Full control over the project’s resources and settings.	Manage all project resources, configure settings, and oversee project operations
Developer	Create and modify agents, tools, workflows, and other project assets.	Build and update agents, tools, workflows, and assets
Tester	Read project resources, run simulations/evaluations, and verify behavior.	Access project resources, execute tests, and validate agent behavior
Viewer	Read-only access to the project.	View project resources and configurations

How workspace and project roles interact:

• Workspace Owners and Admins have workspace-wide authority and can administer all projects without explicit project membership.
• Non-admin workspace members need explicit project membership for project-scoped access.
• When a workspace member creates a project, they automatically become that project’s Owner and can add other workspace members from Settings > Members, even if they’re not workspace Admins.

User Onboarding and Team Management

Only workspace Owners and Admins can manage team membership.

Viewing Current Members

The list shows:

• Name and email
• Workspace role
• Status - active, suspended, locked, or deactivated
• Date joined

Inviting a New Member

1. Click Invite member.
2. Enter the invitee’s email address.
3. Select a role: Admin, Operator, Member, or Viewer.
4. Click Send invite.

The invitee receives an email with a unique link that includes the workspace name and their assigned role. Invitations expire after 7 days and are cleaned up automatically.

Managing Pending Invitations

The Workspace Members page shows a Pending Invitations section for invitations that haven’t yet been accepted.

Action	What it does
Resend	Sends a fresh invitation email with a new token, resetting the 7-day expiry
Revoke	Cancels the invitation so the link can no longer be used

If a team member reports not receiving the invitation email, check the pending list and resend - you don’t need to revoke first.

Changing a Member’s Role

• Find the member in the Members list.
• Click the role dropdown next to their name.
• Select the new role and confirm.

Role changes take effect immediately - the member’s permissions update on their next page load or API call.

Role hierarchy rules the platform enforces:

• You can’t assign a role higher than your own. An Admin can’t promote another member to Owner.
• Only the workspace Owner can promote a member to Admin.
• Only the workspace Owner can transfer ownership.
• You can’t demote yourself - ask another Owner or Admin to change your role.

Removing a Member

• Find the member in the Members list.
• Click the three-dot menu next to their row.
• Select Remove member and confirm.

When a member is removed:

• They lose access to all workspace resources immediately.
• Their project memberships within this workspace are also removed.
• Resources they created (agents, knowledge bases) remain in the workspace.
• Active sessions they initiated continue running, but they can’t start new ones.

Removing a member doesn’t delete their Agent Platform account. They can still access other workspaces they belong to.

Transferring Workspace Ownership

Only the current workspace Owner can transfer ownership.

1. Go to Settings > Team > Members.
2. Click the three-dot menu next to the target member.
3. Select Transfer ownership and confirm by typing the workspace name.

After the transfer, the previous Owner is demoted to Admin, and the new Owner gains full control, including the ability to delete the workspace.