1. In Claude, open Settings › Connectors, find Verdeshell Flow and click Connect — or open its directory page, claude.ai/directory/connectors/verdeshell-flow. (Where the directory isn't offered, such as Claude Code, add a custom connector with the address https://flow-api.verdeshell.com/mcp.)
2. Flow opens. Sign in as usual if you aren't signed in already.
3. On Allow Claude to use Flow?, check the name it shows under Signed in as, pick the Organisation, choose Read only or Read and make changes, and click Allow. Read only is picked for you; choose changes only if you want Claude to work in Flow for you.
4. You're back in Claude. Reads run straight away; Claude asks you before each change (you can adjust this under the connector's Tool permissions).
5. Ask it something about your work.

Belong to several organisations? Each connection is for one organisation. To switch, connect again and pick the other one — Claude then uses the new organisation. The earlier connection stays listed in Your account › Connected apps until you disconnect it, or ends by itself after 30 days unused. Connecting Claude Code on another computer gives that computer its own connection.

A connection lasts up to a year: at least once a year Claude asks you to connect again, and you allow it again on the same screen.

Things to ask

• "What's assigned to me in Flow, and what's due this week?"
• "Summarise ACC-142 and its latest comments."
• "How is the current sprint in the Payments project going?"
• "Which work items mention invoices and are still open?"
• "Find our release checklist in Docs and list its steps."
• With changes allowed: "Create a bug in Payments: refunds over ₹10,000 fail, high priority, assign it to me."
• "Move ACC-142 to In review and comment that the fix is ready."
• "Log 2 hours on ACC-142 for today."
• "Add a 'Decisions' section to the Release checklist page with what we agreed."

• Claude can't delete anything, start or complete sprints, or change members, roles or settings.
• Every change follows your role and the project's rules, exactly as in Flow. A Stakeholder, for example, can comment but not create work items.
• Changes show your name with via Claude beside it, in the work item's history, comments, time log and the Docs page's versions.
• Comments are permanent in Flow — they can't be edited or deleted afterwards.
• Claude won't publish over your unpublished changes to a Docs page; publish or discard them in Flow first. Every earlier version of a page stays restorable.
• By default Claude runs the read-only tools without asking and asks before every change, showing you what it will do. You can adjust this in Claude Settings › Connectors › Verdeshell Flow › Tool permissions; we recommend keeping Needs approval on the tools that make changes. These settings live in Claude, not Flow; on a Claude Team or Enterprise plan a workspace admin can set them for everyone.

Connected apps work on every plan. An Owner or Admin chooses one of three levels:

• Off — disconnects everyone in the organisation at once; nobody can connect until it's turned on again.
• Read only — the starting level. Members can connect Claude to read.
• Read and make changes — members can also let Claude make changes, within their own role.

Moving from changes back to read only keeps everyone connected and pauses Claude's changes from that moment. Moving back to changes resumes them for people who chose Read and make changes; anyone who chose Read only connects again and chooses changes. The same page lists who has connected and what each connection may do, with Disconnect next to each person. Members and Viewers don't see this page.

Click Disconnect next to the connection and confirm. Claude stops reading Flow at once. Removing the connector in Claude stops Claude using it; to end the connection itself, disconnect it here.

You're also disconnected automatically when you change or reset your password, turn on or reset two-factor sign-in, are removed from the organisation, or when Flow sees signs that your sign-in was stolen. Signing out of Flow in your browser does not disconnect Claude. A connection Claude hasn't used for 30 days ends by itself.

• You sign in on Flow's own page; Claude never sees your password.
• Claude gets a key that works for an hour and renews quietly; unused for 30 days, it expires.
• Flow doesn't store your conversations with Claude or log what it asks.
• What Claude reads from Flow becomes part of your Claude conversation, kept under your Claude plan's terms — not Flow's. Anthropic's business plans (Claude Team and Enterprise) don't use your data for model training by default; on a personal plan you choose this in Claude's privacy settings. For work data, use your organisation's Claude business plan, or turn model training off in your personal settings.
• Your workspace includes colleagues' names, comments and work. When you ask Claude about shared work, that reaches Claude too — which is why an Owner or Admin decides whether members may connect apps at all.
• Each connection, disconnection and organisation switch change is recorded in your organisation's security log.

Full details: Privacy policy.

Still stuck? Email support@verdeshell.com.