> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowforma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What it can access

> What FlowForma for ChatGPT can see and do in your FlowForma apps, whose permissions it uses, and how changes go live.

The FlowForma connector works with your FlowForma apps and flows, using your own permissions. It can't see anything you can't already see in FlowForma or SharePoint.

## 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

Before anything is published, ChatGPT shows you a preview of what will change and waits for you to confirm. For what happens next, see [How changes go live](#how-changes-go-live).

For each tool the connector gives ChatGPT, see [Tools](https://docs.flowforma.com/flowforma-for-chatgpt/tools.md). For what it can't build yet, see [Not yet supported](https://docs.flowforma.com/flowforma-for-chatgpt/not-yet-supported.md).

## 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

A few things are worth knowing:

* **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 ChatGPT reads them.
* **People:** a flow names the people assigned to its steps, so ChatGPT 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.

| To do this | You need to be |
| - | - |
| See an app | Someone with access to the app in SharePoint |
| List an app's flows | Someone who can read the app's **Flows** list |
| Read a flow, so ChatGPT can explain, change, or desk test it | A member of the app's FlowForma admin group, a site collection admin, or an admin of that flow |
| Look up the app's SQL connections, procedures, and tables | A member of the app's FlowForma admin group, or a site collection admin |
| Check a flow against your site, publish it, or switch it on or off | A member of the app's FlowForma admin group, or a site collection admin |

A site collection admin is an administrator of the whole SharePoint site the app is in. Anyone signed in can ask ChatGPT to build and desk test a new flow.

> [!NOTE]
>
> 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 ChatGPT works the same way as saving it in the FlowForma designer. There's no separate draft stage in FlowForma.

1. ChatGPT 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.
2. You confirm, and ChatGPT prepares the flow for publishing. This runs the same check against your site again.
3. ChatGPT asks you to approve publishing it. A prepared publish lasts 10 minutes, so if you take longer to approve, ChatGPT prepares it again.
4. FlowForma publishes the flow to your app.

What happens next depends on the flow:

* **A new flow** is switched on if a flow licence is available.
* **An updated flow** keeps its current on/off state.

If someone else changes the flow after ChatGPT has read it, FlowForma stops the publish rather than overwrite their change. Ask ChatGPT to read the flow again, then repeat your change.

If a publish fails partway, FlowForma removes what it had added where it can. Open the flow in FlowForma and check it before you try again.

### Undo a change

A publish can't be undone with one click, so keep a copy first:

1. Before a big change, [export the flow](https://docs.flowforma.com/product/the-flowforma-site/import-export.md#export-a-flow) from FlowForma as a backup.
2. To reverse a change, ask ChatGPT to change the flow back, then publish it again.

> [!TIP]
>
> Try new flows and bigger changes in a test app first, then publish them to your live app once you're happy.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.