Overview

Contox supports team collaboration through role-based access control (RBAC), project-level visibility settings, and shared project brains. When your team uses Contox, every member benefits from the collective knowledge captured across all sessions.

RBAC roles

Contox defines three roles with progressively broader permissions:

Owner

The team creator. There is exactly one owner per team.

• Full access to all team resources
• Manage billing, subscription, and payment methods
• Delete the team
• Manage all members (invite, remove, change roles)
• Manage all projects regardless of visibility

Admin

Trusted team managers who help organize projects and members.

• Invite and remove team members
• Change member roles (except the owner)
• Create, update, and delete all projects
• Access all project data regardless of visibility
• Cannot manage billing

Member

Standard team members who work on projects.

• Create new projects
• Access public projects (read and write)
• Access private projects only if explicitly added
• Read and write memory items
• Trigger enrichment
• Cannot invite or remove team members

Permission matrix

Project-level access

Public projects

Public projects are accessible to all team members. Any member can:

• View the project brain and memory items
• View sessions and events
• Trigger enrichment
• Create and update contexts

Use public visibility for shared repositories that the whole team works on.

Private projects

Private projects are only accessible to explicitly added members. Use private visibility for:

• Personal projects
• Sensitive codebases
• Projects in early development that are not ready to share

Adding members to private projects

1. Open the project settings
2. Go to the Members section
3. Click Add Member
4. Select a team member and assign a role
5. Click Add

Shared brain

When multiple team members work on the same project, they share a single project brain:

• Everyone contributes -- Sessions from all members feed into the same enrichment pipeline
• Everyone benefits -- The brain includes knowledge from all contributors
• No conflicts -- Memory items are additive; the enrichment pipeline handles deduplication
• Attribution -- Items track their source session, so you can see who contributed what

How shared brains improve results

When Developer A fixes a bug and saves the session, the fix is enriched and added to the brain. When Developer B starts a new session the next day, their AI assistant already knows about the fix. This prevents duplicated effort and ensures consistency.

Collaboration patterns

Pair programming with AI

Both developers in a pair can use Contox independently. Their separate sessions are enriched into the same brain, capturing both perspectives.

Team stand-ups

Review recent sessions in the dashboard to see what the team has been working on. The memory items provide a structured summary of each developer's contributions.

Knowledge handoffs

When a developer transitions off a project, their accumulated session knowledge remains in the brain. The incoming developer gets the full benefit of previous work.

Code reviews

Memory items from enrichment often highlight architectural decisions and conventions that are relevant during code reviews. Reference the brain for context about why code was written a certain way.

Next steps

• Dashboard Team -- Manage team members in the UI
• Team API -- Manage team programmatically
• Projects -- Configure project visibility