# Team Access

> Invite your team to chat with your AI agent. Each person gets their own conversations, their own context, and independent token usage.

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

```mermaid
flowchart TD
    A["Alice"] -->|"own conversations"| W["Workspace\n+ Agent"]
    B["Bob"] -->|"own conversations"| W
    C["Charlie"] -->|"own conversations"| W

    W --> T1["GitHub MCP"]
    W --> T2["Notion MCP"]
    W --> T3["Slack MCP"]
    W --> T4["Custom Functions"]

    style A fill:#3b82f6,stroke:#2563eb,color:#fff
    style B fill:#10b981,stroke:#059669,color:#fff
    style C fill:#f59e0b,stroke:#d97706,color:#fff
    style W fill:#1e293b,stroke:#6b7280,color:#fff
    style T1 fill:#1e293b,stroke:#6b7280,color:#fff
    style T2 fill:#1e293b,stroke:#6b7280,color:#fff
    style T3 fill:#1e293b,stroke:#6b7280,color:#fff
    style T4 fill:#1e293b,stroke:#6b7280,color:#fff
```

- **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

1. **Invite Team Members to Your Workspace**

   1. Open the [Admin Dashboard](https://app.aerostack.dev)
   2. Go to **Workspaces** → select your workspace → **Members** tab
   3. Click **Invite Member** and enter their email
   4. They receive an invitation email and join the workspace

   Each member gets their own workspace token (`mwt_` prefix).

2. **Each Member Connects Their Agent**

   Share the setup instructions with your team. Each person adds the Aerostack Bridge to their own agent configuration using their personal token:

   First install: `npm install -g @aerostack/gateway`

   Then add to their MCP config:

   ```json
   {
     "mcpServers": {
       "aerostack": {
         "command": "aerostack-gateway",
         "env": {
           "AEROSTACK_WORKSPACE_URL": "https://mcp.aerostack.dev/ws/your-workspace-slug",
           "AEROSTACK_TOKEN": "mwt_their_personal_token"
         }
       }
     }
   }
   ```

3. **Everyone Chats Independently**

   Each team member opens **Agent Chat** in the dashboard and starts their own conversations. The workspace owner can see all team activity in the dashboard.

---

## What Each Team Member Gets

| Feature | Details |
|---------|---------|
| **Own conversations** | Each person's chats are completely separate |
| **Own token** | Independent rate limits (120 req/min per person) |
| **Own analytics** | See how much each person uses the agent |
| **Own approvals** | Each person approves their own risky tool calls |
| **Shared tools** | Everyone accesses the same MCP servers, skills, and functions |

---

## 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:

| Plan | Members |
|------|---------|
| Free | 1 (owner only) |
| Starter | 5 |
| Pro | 20 |
| Business | 100 |
| Enterprise | Unlimited |

Need more seats? [Upgrade your plan](/billing).

---

## 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.

Removing a member does not delete their conversation history. The workspace owner can still see past conversations for audit purposes.

---

## Next Steps

- [Connect OpenClaw](/agent-chat/connect-openclaw) — setup guide for connecting agents
- [Approvals](/agent-chat/approvals) — control what the agent can do for each team member
- [Token Savings](/agent-chat/token-savings) — team conversations cost less because each is isolated