Every folder answers two questions, and everything else follows from them. Both are in the folder's Settings, at the top.
No sharing — the folder stays on this machine. Issues are kept in a file inside it. This is solo use.
GitHub — the folder is a git repository that you pull and push yourself, the usual way. Stood Flows doesn't move graph files for you; what it does is keep the folder's issues in GitHub, so the team works on them there.
S3 — Stood Flows publishes and pulls the whole analysis through a shared bucket, issues included. Nobody except the person publishing needs Salesforce access. See Team sharing (S3).
Admin — you produce the analysis. You refresh graphs from the org and, where the sharing method allows it, publish the results. Admins need a licence key.
Contributor — you consume it. You read the insights, raise issues, comment on them and close them. No licence key needed, and nothing to run or break.
Once you've answered both, Settings shows only the fields your answers actually need — a licence key for an Admin, a repository for GitHub, bucket details for S3 — and lists the buttons your choices produce, so you can check the setup without leaving the page.
Refreshing a graph from a Salesforce org is the licensed action. That's true whether you hand the result to a team or keep it to yourself, so a solo Admin needs a key just like a team one does.
A Contributor never needs one. That's the point: you can hand someone a folder and they're useful in it straight away.
Keys are tied to the orgs they were issued for, so having a key doesn't let you refresh somebody else's org — see License keys.
The buttons sitting next to New Graph change with your two answers:
Sharing | Role | Buttons |
No sharing | Admin | Full analysis |
No sharing | Contributor | — |
GitHub | Admin | Full analysis |
GitHub | Contributor | — |
S3 | Admin | Publish all, Full analysis |
S3 | Contributor | Refresh all, Publish issues |
Publish all and Refresh all never appear together. The person producing the analysis pushes it out; everyone else pulls it in. That way nobody overwrites their own work.
Whichever combination you land on, every view stays fully browsable: KPI table, Apex trees, Licensing, DML, I/O, History and the dashboards. A Contributor simply has nothing to run.
Dashboard and Settings sit to the left, separated from the action buttons — those two are navigation and are always there.
A button your setup can never use isn't shown at all, so the toolbar only ever offers you things that make sense.
A button that is shown but greyed out is one you should have, blocked by something you can fix. Hover it and the tooltip tells you what: a licence key that has expired, a key that doesn't cover this org, or S3 details you haven't filled in yet.
Both answers can be changed at any time, and nothing is lost when you do. Switching from No sharing to S3 keeps the analysis you already have — you just gain somewhere to publish it. Switching role changes which buttons you see, not what's in the folder.
Folders created before these settings existed keep working exactly as they did: Stood Flows reads what they were already set up for and pre-selects it for you.