What you can do
Explore your apps and flows
- List the FlowForma apps you can open, and the flows in each one
- Get links to open an app, open a flow in the designer, or start a new form
- Read a flow and explain it: its steps, the questions on each step, rules, routes, and the lists and documents it uses
Build and change flows
- Build a new flow from a process you describe
- Change an existing flow, for example add a question, change an approver, or update a rule
- Look up your app’s SQL connections, stored procedures, and tables, to build SQL lookups and rules
- Desk test a flow without running it: every route and what decides it, when each question shows and hides, who gets each step, and suggested improvements
- Check a flow against your site, to find missing lists, columns, people, or permissions before you publish
Publish flows to FlowForma
- Publish a new flow to an app, or an update to an existing flow
- Switch a flow on or off
What it doesn’t touch
The connector works with flow definitions, not the data that runs through them. It doesn’t:- Read, submit, or change form submissions
- Read the documents in your libraries
- Read the data in your databases
- Change the items already in your SharePoint lists
- Delete flows, or create or delete apps
- Lists a flow needs: publishing can create a list the flow needs, with any starting rows the flow defines, and add a column an existing list is missing. When you move a flow to another app, you choose whether its lists are created empty, copied with their rows, or left pointing at the original lists.
- Templates: a flow’s document and email templates are part of the flow, so Claude reads them.
- People: a flow names the people assigned to its steps, so Claude sees those names.
- Flows that start other flows: if a flow starts another flow, publish the flow it starts first, into the same app.
Who can see and change what
The connector always works as the person signed in. There’s no shared service account behind it, so SharePoint and FlowForma permissions decide what each person can see and do.
A site collection admin is an administrator of the whole SharePoint site the app is in. Anyone signed in can ask Claude to build and desk test a new flow.
Write access to the Flows list on its own isn’t enough to publish a flow. You need one of the admin roles above.
How changes go live
Publishing a flow from Claude works the same way as saving it in the FlowForma designer. There’s no separate draft stage in FlowForma.- Claude shows you a preview of what will change. Before an update, the preview also lists any change to who can see or act on the forms, or to what’s recorded.
- You confirm, and Claude prepares the flow for publishing. This runs the same check against your site again.
- Claude asks you to approve publishing it. A prepared publish lasts 10 minutes, so if you take longer to approve, Claude prepares it again.
- FlowForma publishes the flow to your app.
- A new flow is switched on if a flow licence is available.
- An updated flow keeps its current on/off state.
Undo a change
A publish can’t be undone with one click, so keep a copy first:- Before a big change, export the flow from FlowForma as a backup.
- To reverse a change, ask Claude to change the flow back, then publish it again.

