Approve what Claude Desktop proposes

In the portal, under Environments, click Development, and there Open. Flow opens in a new tab and you are signed in straight away.

Your colleague Iris's Claude Desktop has proposed four things, your own Claude Desktop one. At the bottom of the explorer, under Workspace-wide, is Proposals with a counter of what is waiting. An AI app never changes access itself: it proposes, a person decides.

Every proposal has two sides. On the left is why, in the app's words: read it as an explanation, not as an instruction. On the right is what happens if you approve, worked out by Flow itself: here Tom gets the role Reader through a team, and which rights and dashboards come with it. Below the title you see which app proposed it, on whose behalf (here Iris), and when the proposal expires (after seven days).

Click Approve and confirm. Flow carries it out at once, with your rights: if you yourself may not manage people, or the role gives more than you have, Flow refuses in plain words. The audit log says you approved a proposal from Claude Desktop.

The app wants to share the weekly overview with an open link, valid for sixty days. Flow already checked that every source is internal or public. After approving, Flow shows the link once, to you: the app never gets it, it only hears that the dashboard is shared. Copy the link and pass it on deliberately.

The app needs the wholesaler's API key. It does not ask for it in the chat, but with request_secret: a request a person sets secret groothandel-api. Flow says what it is for (connections to api.groothandel.nl) and that the app never sees the value. Type or paste the key in the field and click Set value. The value goes straight into the vault, as version 1; the app only hears the name and the version number.

The third proposal maps a group from your sign-in system to the role Administrator. Flow itself says what that means: whoever manages that group makes someone an administrator here. Click Reject, write why and confirm: the app reads your reason back and can propose a more limited role.

The last proposal comes from your own Claude Desktop: a second MCP key. On access you yourself ask for (through your app), someone else decides: four eyes. An app steered by a text in a table or document so never gets more access with one click of its own person. The card says who can approve it, and Approve is off. If there is nobody else, Flow says how to add someone; you can also reject it and arrange it yourself on the screen.

Open the Decided tab: per proposal who decided, when, and for a rejection the reason. Claude Desktop asks for the status with get_proposal and so hears approved (with what was done, without keys or links), rejected (with your reason) or expired.