Teams
Set up a shared workspace where everyone's mapping compounds.
This path covers the team-specific setup on top of the Solo Hunter loop. Everything in the core loop still applies — teams just share it.
1. Create the shared workspace
One person creates the workspace and owns it. A workspace is the unit of sharing: the component library, playbooks, and outcomes inside it belong to everyone in it.
Details: Account and Workspaces.
2. Invite your members
From workspace settings, invite teammates by email — or share the invite link. Each invite carries a role:
- Admin — manages workspace settings, members, and everything inside.
- Member — full access to the vault's content.
Details: Share and Collaborate.
3. Seed and shape the library together
Seed the Starter Library, then treat the library as an institutional asset: anyone can add components, and every addition makes everyone's suggestions smarter. Encourage the library discipline — reusable, observable, atomic.
4. Keep engagements separate, reuse the setup
Give each client or engagement its own workspace, and use Clone Workspace to carry over the parts worth reusing — programs & assets, components, playbooks.
Details: Clone a Workspace.
5. Share single things when that's enough
Not every collaboration needs an invite. Any asset, playbook, or component can be shared as a read-only snapshot link — useful for a second opinion or a client review.
Details: Share and Collaborate.
6. Connect your agents
If your team works with AI agents, each member can create their own agent connection — scoped to the workspace, capped per member, revocable, and audited.
What's next
- Manage Your Scope — keep large team scopes navigable.
- The CAVET Method — a shared vocabulary is what makes team knowledge compound.