Team Plans: Seats, Roles, and Shared Workspaces

Chase Agents is built for teams. Higher-tier plans include more seats, enabling your whole team to collaborate on automations, share connections, and interact with AI agents from a single workspace. This guide explains how team billing works and how to get the most from a shared workspace.

What Is a Seat?

A seat is a user slot in your workspace. Each person who is a member of the workspace occupies one seat. The default number of seats included with each workspace is 3. Additional seats are available on paid plans and can be added through the billing panel. The workspace owner counts as a seat. Pending invitations do not consume a seat until the invite is accepted.

Workspace Roles

Chase Agents has two primary workspace roles: Admin and Member. Admins can manage billing, invite and remove members, create and edit all automations, manage all connections, and view the audit log. Members can use agents, run automations, and view workflow history. Workspace settings such as billing, member management, and connection access configuration are restricted to admins.

Inviting Team Members

Workspace admins can invite members from the Workspace People page. Enter the invitee's email address and select their role. The invitee receives an email with an invite link. When they click the link and complete account creation, they are added to the workspace and their seat is consumed. Admins can view pending and accepted invitations from the same page.

Shared Connections

Connections marked as WorkspaceWide are available to all workspace members. This is ideal for shared service credentials like a CRM or a team Slack workspace. Connections marked as Personal are only available to the user who created them. SpecificTeamMembers connections can be scoped to a defined list of users. Admins manage connection access settings from the connections panel.

Shared Automations

All automations in a workspace are visible to all workspace members. Any admin can edit any automation. Workflow History for all automations is accessible to all members, giving the team full visibility into what is running and what the results are. Action consumption counts are shared across the workspace: all automations regardless of who built them draw from the same monthly action quota.

Removing a Member

Workspace admins can remove members from the Workspace People page. Removing a member immediately revokes their workspace access. Any Personal connections they created remain associated with their account and will not be available for use by other workspace members after removal. Automations they built remain in the workspace and continue to run.

MCP API Access for Developers

Higher-tier plans include access to the Chase Agents MCP HTTP endpoint, which allows external AI clients like Claude Desktop or Cursor to connect to your workspace and use your automations and agents as MCP tools. The workspace API key for MCP access is managed from the workspace settings panel. Only workspace admins can view and rotate the workspace API key.