Claude Team and Enterprise

In a Team or Enterprise organisation, Claude and other MCP clients stay out until an owner asks for them. Once MCP is on, each member connects their own Claude app and works with their own roles, under the organisation's classification ceiling.

Before you start

• You are an owner of the iyedy organisation.
• Decide which Claude apps your members may use. iyedy knows two: Claude (claude.ai, Claude Desktop, the mobile apps) and Claude Code.
• Check the classification of the diagrams your members will ask about. Claude never reads above the organisation's ceiling, Internal by default.

Turn MCP on for the organisation

1. Write to support

   There is no setting for this in iyedy yet. Write to support@iyedy.com from the address of an owner, name the organisation, and say which clients you allow: Claude, Claude Code, or both. On Enterprise, the list of allowed clients is required.

2. Tell your members

   Once support confirms, send your members the guide Connect iyedy to Claude. Each member connects their own Claude app and signs in with their own iyedy identity. On a Claude Team or Enterprise plan, the Owner of the Claude organisation adds the connector first: see On Claude's side.

3. Check one connection

   Ask one member to connect and to ask Claude for the list of their iyedy diagrams.

   The member sees the organisation's workspaces they belong to, and no message saying that MCP clients are turned off.

On Claude's side

On a Claude Team or Enterprise plan, an Owner of the Claude organisation adds iyedy for everyone, then each member connects their own account. Claude's help describes two ways.

From the directory (recommended). The Owner opens claude.ai/directory/iyedy (or Customize › Connectors, Discover, then searches for iyedy) and selects Connect for your team. Members then select Connect to Claude on the same page and sign in with their own iyedy identity. Until the Owner has added it, members see Request or a note to ask an Owner.

As a custom connector, by its address. Members without the Owner role cannot add it themselves:

• The Owner goes to Organization settings › Connectors, selects Add, then Custom (and Web if Claude asks for the type), names it iyedy and enters https://app.iyedy.com/mcp. If the dialog shows Advanced settings, leave them empty. If it shows the settings it detected after Continue, keep Sign in now and Use Claude's published identity. Then select Add.
• Each member then finds iyedy under Customize › Connectors, with the Custom label, and selects Connect to sign in with their own iyedy identity.

This is Claude's setting, separate from iyedy's: MCP must also be on for your iyedy organisation (above).

What each member can reach

• Their own access, never more. Claude acts as the member: the same workspaces, diagrams and roles. A diagram they cannot open does not exist for Claude.
• Up to the ceiling. In Team and Enterprise, MCP clients read up to Internal. A Confidential or Restricted diagram is never listed, found by a search or reached by an impact analysis.
• No change without a person. Claude can submit a proposal only where the member is at least a contributor, and an editor of the diagram applies or rejects it in iyedy.
• Single sign-on holds. When your organisation enforces single sign-on, a member's connection works only if they signed in through it, with their work e-mail address. Guests keep their own sign-in.

Allowed clients are not a guarantee

What iyedy records

Every call that reads or proposes in the organisation is recorded in its audit log: the tool, the client, the permissions used and the result. A call the organisation's policy refuses is recorded too, with the reason. Diagram content and tokens are never recorded.

If it doesn't work

More symptoms: Claude troubleshooting.