Using Armbrain with a Claude Team

Set up Armbrain once for a Claude Team or Enterprise organization, then let each teammate connect with their own Armbrain identity.

What the organization setup does

A Claude organization Owner or Primary Owner adds the Armbrain connector to the organization's approved connector list. Each member then connects and authenticates separately.

The organization setup does not share the owner's Armbrain account, API key, or permissions. Claude sends each member's requests under that member's own Armbrain identity.

1. Invite teammates to the shared mind

Before teammates connect Claude, give each person access to the Company Mind:

Sign in at hq.armbrain.io.
Open Settings > Team & seats.
Find the Company Mind and click Invite.
Enter the teammate's work email and choose an access role.
Repeat for each teammate.

Armbrain creates or reuses an account for each email and sends individual sign-in instructions. Never paste the owner's API key into another person's Claude account.

Choose the role by data access

Role	Reads	Writes	Best fit
Editor	All memories, including sensitive and CMO-only	Yes	Executives who may see compensation, equity, and confidential strategy
Contributor (`va`)	Open memories only	Yes	Managers who need operational context and shared EOS work
Viewer	Open memories only	No	Read-only observers

For a manager who must work in the Company Mind but must not see compensation or equity, choose Contributor. Do not choose Editor.

2. Add Armbrain to the Claude organization

These steps follow Claude's current custom-connector instructions:

As a Claude organization Owner or Primary Owner, open Organization settings > Connectors.
Click Add.
Hover over Custom, then choose Web.
Enter https://api.armbrain.io/mcp as the remote Model Context Protocol (MCP) server URL.
Name the connector Armbrain and click Add.

Do not enter the Armbrain owner's API key or login in the organization settings. Adding the connector makes it available to the organization; it does not authenticate members.

3. Have every teammate connect individually

Each teammate completes these steps in their own Claude account:

Open Customize > Connectors.
Find the Armbrain custom connector.
Click Connect.
Sign in to Armbrain with the same email address that received the mind invitation.
Approve the connection.
In each new conversation, click +, open Connectors, and enable Armbrain for that conversation.
In Claude, say: Switch to the Company Mind.

Each teammate must click Connect and complete Armbrain authentication. The Claude organization owner cannot authenticate on the team's behalf.

4. Verify role scoping before rollout

Test with one manager account before inviting the whole leadership team:

Store a normal operational memory in the Company Mind.
Store this test memory: Test executive ownership: Alice holds a 5% stake. Armbrain automatically classifies that ownership statement as CMO-only.
Connect as the manager with the Contributor role.
Confirm the manager can find the operational memory.
Confirm the manager cannot find the sensitive test memory.
Delete the test records after verification.

Sensitivity roles protect Armbrain memories. EOS fields are shared operational data, so do not put compensation or equity into rock titles, scorecard metrics, issue titles, L10 agenda items, task titles, or other shared EOS fields. Store executive-only details as sensitive or CMO-only memories, or keep them in a separate private mind.

Shared EOS workflow

Once connected, teammates can work from their own Claude sessions against the same Company Mind:

Show the Company Mind scorecard.
Mark the hiring rock off track.
Add an issue: dispatch callbacks are slipping.
Prep the next L10.
Store this operational decision in the Company Mind.

Changes land in the shared Armbrain data, so the next teammate sees the same rocks, scorecard, issues, decisions, and L10 context. Armbrain access roles still apply to every member.

Individual Pro or Max setup

For an individual Claude plan, open Customize > Connectors, click Add custom connector, and use https://api.armbrain.io/mcp. Then complete the same individual Armbrain sign-in.

Troubleshooting

Armbrain is missing from the connector list

A Claude organization Owner or Primary Owner must add it under Organization settings > Connectors first.

The shared Company Mind is missing

Confirm that the email used to sign in to Armbrain exactly matches the email invited under Settings > Team & seats. The mind grant belongs to the Armbrain identity, not to the Claude organization itself.

A manager can see executive-only content

Remove access immediately, then check both conditions:

The member must have the Contributor or Viewer role, not Editor.
Executive content must be stored as sensitive or CMO-only memory, not in a shared EOS field.

Authentication fails

Disconnect Armbrain in Claude, reconnect it, and sign in with the invited teammate's own Armbrain account. Never paste the owner's API key as a workaround.