How proposals reach your team

A change from Claude or another MCP client is stored as a proposal. It waits in iyedy until a person who can edit the diagram applies or rejects it.

No MCP client can change a diagram. When Claude, or another client, has a change ready, it stores it as a proposal. The proposal waits in iyedy, and a person decides. This page follows a proposal from Claude Code to the diagram.

From Claude to iyedy

1. Claude previews the change. It sends the whole proposed definition of the diagram and gets back, without anything being stored, whether it is valid, what it adds, removes and changes, and which findings it introduces or resolves.
2. Claude submits it. Claude asks for your approval first. iyedy checks the change again and stores it with the client's name, your name, the version it starts from and the reason Claude gave. An invalid change is refused, and nothing is stored.
3. The proposal waits. Its status is open. The diagram has not changed.

What the reviewer sees

Anyone who can edit the diagram opens it in iyedy, then the Assistant panel (Ctrl J). Above the conversation, Proposals to review lists the open proposals, each with:

• who made it, for example “Proposed by Claude Code for Alex Morgan”;
• the counts of what it adds, changes and removes, its date, and the findings it would add;
• a warning when the diagram changed since the proposal was made: the rows then compare it with the diagram as it is now.

Review lays the proposal out like a proposal of the Assistant: one row per change, ghosts on the canvas, and the reason given. Rows that touch security start unticked, so a person looks at each one. Then:

• Apply applies the rows you kept, in one step you can undo, and iyedy saves a version;
• Reject turns the proposal down;
• Set aside closes it without deciding: it stays open for later.

The decision is always made in the app, by a person signed in. No token and no MCP client can apply or reject a proposal.

After the decision

Claude sees the status of its proposals (open, accepted, rejected, withdrawn) and whether the diagram moved since. While a proposal is open, its author can take it back: in iyedy with Withdraw, or by asking Claude.

Limits

• 30 days. A proposal nobody handles expires and is deleted 30 days after it was made.
• Open proposals are capped. At most 50 open proposals per diagram and 10 per author. Over that, a new one is refused until some are handled.
• The contributor role. Only someone with at least the contributor role in the workspace can submit a proposal.
• Recorded, not read. In an organisation, submitting, deciding and withdrawing are recorded in the audit log by ids and counts, never with the proposed content.

What this means for you

Let Claude draft; keep the decision with the people who own the diagram. When you review, read the reason, look at the security rows, and apply only what you would have drawn yourself. Proposals from iyedy's own Assistant can wait for review the same way: see Ask, review, apply.