Maindex Teams
How to create a team, join one, use team memory from your agents, and manage what gets written.
1. Who this is for
This guide covers Maindex Teams end to end. If you just want to know what Teams is, start at Teams. If you're deciding whether to buy, pricing has the plan limits.
2. Getting started (you were invited)
- Accept the invite from the email, or open Dashboard → Teams → Pending invites. Invites expire after 7 days.
- The email on the invite has to match the one you're signed in with.
- Accepting needs a plan that includes team access: either plan does.
- You land in the team's collections at whatever role you were invited as.
- Connect an agent (see §5) and you're reading team memory.
Your daily read and write totals on this team are visible to its managers. Nothing else about your account is.
3. Creating a team
Requires a plan that includes team creation (Galaxy Brain).
- Dashboard → Teams → Create team
- Pick a name and a slug: global, permanent, prefixes everything (
acme:runbooks,acme:mem-4f). Cannot be changed later. - Name your first collection (often "General" /
general): you choose name and slug. - Invite people by email with a role.
Pending invites count toward the member limit: cancel stale ones if you're near the cap.
Plan limits (current)
Expanding Brain: $14.99/mo
- Join unlimited teams
- Generous monthly synapse quota
Galaxy Brain: $49.99/mo
- Create unlimited teams
- Generous monthly synapse quota
- 20 personal collection locks
- Join unlimited teams
4. Roles and permissions
| Can they… | Viewer | Editor | Manager | Owner |
|---|---|---|---|---|
| Read team memories | ✓ | ✓ | ✓ | ✓ |
| Write team memories | ✓ | ✓ | ✓ | |
| Invite people | If editors may invite | ✓ | ✓ | |
| Review queue / shadow | ✓ | ✓ | ||
| Audit log / analytics | ✓ | ✓ | ||
| Create collections | By delegation | ✓ | ✓ | |
| Transfer / delete team | ✓ |
Viewers cannot copy team memories into personal collections: read access should not quietly become export access. Whether editors can send invites depends on the team collection's invite policy.
5. Using Teams with your agents
No new connection. Your existing MCP URL already works.
Tools with optional team: memory_keep, memory_search, memory_recall, memory_list, collection_manage.
- Omit
team: personal + every team, each labelled team: "personal": personal onlyteam: "acme": that team only
Team writes must be explicit. IDs: acme:mem-4f is team; bare mem-4f is personal. Prefix collection slugs (acme:runbooks) when ambiguous.
6. Automated review
Every team write runs through our server-side review pipeline. Fast automated checks run first; ambiguous or higher-risk content gets a full agentic review before the team can see it.
We screen for prompt injection, secrets and API keys, injected instructions, and profanity. Most writes publish immediately. Flagged writes wait in the manager review queue, and the writing agent is told what happened on its next call.
7. Personal and team memory
Managers never see your personal memories. Copying always creates a new memory with a new ID. A setting can block agents from moving personal memories into team collections.
8. For managers
Review queue: Dashboard → Teams → team → collection → Review. Audit log is append-only. Analytics show coarse per-member daily totals. Export any collection to JSON; shadow content excluded.
9. Billing
Everyone can pay for themselves, or one person can cover the team on one invoice. Same plan prices either way. Synapses bill to whoever's agent made the call. If an owner's billing lapses, the team freezes; a manager on a create-tier plan can claim it.