Team Setup

Set up your team.

Invite team members, assign roles, and share context across your organization. Team workspaces let everyone's AI assistants access shared memory and decisions.

How it works

Workspace, members, shared projects.

Workspace

Your team's shared container.

Team members

Invite colleagues with roles.

Shared projects

Everyone accesses the same context.

When you invite team members to a workspace, they can use ContextStream tools in their own AI editors and share the same project memory. Decisions captured by one team member are visible to everyone.

Capabilities

What teams get in every session.

Team plans unlock shared execution scope beyond basic invite/roles. Once MCP is configured against a team workspace, every session(action="context") call can surface team-aware guidance automatically.

Shared workspace memory

Decisions, docs, plans, and indexed project context stay in the team workspace — not siloed per editor.

Team context surfacing

Priority tickets, governance cues, recommendations, and linked artifacts appear in session(action="context") responses.

Skill sharing & discovery

Publish reusable workflows with skill(action="share", scope="team"); teammates discover them via matched skills.

Tickets, handoffs & releases

Create and assign entity records (tickets, handoffs, incidents) with indexed refs instead of brittle URLs.

Account mode control

Dual-context accounts switch team vs personal scope via --account-mode or session set_account_mode.

Team-safe governance

Transcript bodies stay owner-only; topic signals and team discussions respect workspace visibility rules.

Setup tip: When the MCP wizard detects a team-capable account, it shows workspace selection tips and non-interactive refresh commands after completion. See CLI shortcuts and the post-login team checklist.

Automation

Non-interactive CLI shortcuts.

Use these after onboarding teammates, upgrading MCP, or switching to a shared team workspace. Full details on the MCP docs page.

team refresh · common commands

# Refresh hooks after joining a team workspace
contextstream-mcp update-hooks --scope=global

# Regenerate rules for all editors (includes team workflow guidance)
contextstream-mcp update-rules --scope=all

# Rewrite MCP configs (credential rotation / workspace change)
contextstream-mcp update-configs --scope=global

# Migrate legacy local configs to hosted remote (default)
contextstream-mcp migrate-remote --scope=all

# Script editor detection + config generation
contextstream-mcp detect-editors --format=json
contextstream-mcp generate-configs --transport=remote --preauth

Onboarding

Six steps to a connected team.

Step 01

Create or select a workspace

If you don't have a workspace yet, create one. This will be your team's shared container for projects and context.

Tip:Use a descriptive name like “Acme Engineering” or “Product Team” so members know which workspace to join.

Step 02

Invite team members

Go to your workspace's Settings → Team page to invite members:

1.Click Invite Member
2.Enter their email address
3.Select a role (Admin, Member, or Viewer)
4.They'll receive an email invitation

Invited members will receive an email with a link to accept the invitation. If they don't have a ContextStream account, they'll be prompted to create one.

Step 03

Accept the invitation

When invited, members receive an email with a prominent Accept Invitation button. Clicking it will:

•Log them in (or prompt signup if new)
•Add them to the workspace with their assigned role
•Redirect them to the workspace dashboard

Step 04

Select the workspace

Once a member joins, they can switch between workspaces using the workspace selector in the dashboard sidebar. Each workspace has its own projects and context.

Step 05

Install MCP in their editor

Each team member needs to configure the ContextStream MCP server in their AI editor. The easiest way is to run the setup wizard.

terminal · macOS / linux

curl -fsSL https://contextstream.io/scripts/mcp.sh | bash

powershell · windows

irm https://contextstream.io/scripts/mcp.ps1 | iex

Alternative: npx (requires Node.js 18+)

terminal · npx

contextstream-mcp setup

The wizard will authenticate them and configure their editor (Cursor, VS Code, Claude Code, etc.) to use the team workspace.

Step 06

Start using shared context

Now everyone on the team can:

Access the same project memory and decisions
Capture decisions that the whole team can recall
Search shared context across all projects
Use knowledge graphs to understand relationships

Roles

Member roles

Each workspace member has a role that determines their permissions.

Owner

Workspace creator with full control

All admin permissions
Delete the workspace
Transfer ownership
Manage billing

Admin

Can manage members and settings

Invite and remove members
Change member roles
Manage integrations
Configure workspace settings

Member

Standard team member access

Read and write content
Create and edit projects
Capture decisions and memory
Use all MCP tools

Viewer

Read-only access

View projects and memory
Search context
Cannot edit or create content

Seats

Seat limits

Your plan determines how many team members can join a workspace.

Plan	Team seats	Notes
Pro	1	Individual professional use
Team	3 minimum	Team collaboration (3-seat minimum)
Enterprise	Unlimited	Custom seat allocation

Reached your seat limit? You can view current usage in your workspace's Team settings. Upgrade your plan to add more team members.

Administration

Managing your team

Admins and owners can manage team members from the Settings → Team page.

Invite members

Send email invitations to colleagues. Choose their role when inviting.

Change roles

Promote members to admin or change their access level anytime.

Remove members

Remove members who no longer need access. They'll lose access to all workspace resources.

Next steps

Get the most out of ContextStream.

Once your team is set up, explore these guides.

MCP integration

Configure MCP in your AI editor.

Read

Quickstart guide

Get up and running in 5 minutes.

Read