Team Access

Give your entire team access to your AI agent in minutes. Each team member gets their own conversations — no shared history, no cross-talk, no context pollution. Everyone talks to the same agent with the same tools, but each person’s chat is completely independent.

How It Works

• Alice asks the agent to create a GitHub issue — her conversation only has her messages
• Bob asks the agent to summarize Notion pages — his conversation is completely separate
• Charlie asks about deployment status — no idea what Alice or Bob asked

Everyone shares the same workspace tools, but conversations are isolated.

Set Up Team Access

{
  "mcpServers": {
    "aerostack": {
      "command": "npx",
      "args": ["-y", "@aerostack/gateway"],
      "env": {
        "AEROSTACK_WORKSPACE_URL": "https://mcp.aerostack.dev/ws/your-workspace-slug",
        "AEROSTACK_TOKEN": "mwt_their_personal_token"
      }
    }
  }
}

What Each Team Member Gets

What the Workspace Owner Sees

As the workspace owner, you have a complete view across the team:

• All conversations — see every team member’s chat history
• Per-member analytics — who is using which tools, how often
• Per-member token usage — track costs per person
• Approval history — review what each person approved or rejected
• Activity feed — real-time view of all agent actions across the team

Use Cases

Engineering Team

Set up a workspace with GitHub, Linear, CI/CD, and documentation tools. Each engineer chats with the agent about their own tasks — reviewing PRs, creating issues, checking build status — without cluttering each other’s context.

Support Team

Connect your knowledge base, ticketing system, and CRM. Support agents each have their own conversations for handling different customer issues simultaneously.

Agency / Client Work

Create separate workspaces per client. Invite the relevant team members to each workspace. When a project ends, remove access in one click.

Cross-Functional Team

Product, engineering, and design all connect to the same workspace. The PM asks about metrics, the engineer asks about deployments, the designer asks about component docs — all using the same tools, all in separate conversations.

Seat Limits

The number of team members per workspace depends on your plan:

Need more seats? Upgrade your plan.

Removing a Team Member

Go to Workspaces → Members → click Remove next to the person. Their token is revoked instantly. Their agent loses access immediately. No cache delay.

Next Steps

• Connect OpenClaw — setup guide for connecting agents
• Approvals — control what the agent can do for each team member
• Token Savings — team conversations cost less because each is isolated