Stood Flows can publish a folder's results to an S3 bucket so teammates can pull them — without anyone else needing Salesforce access. It works with Amazon S3 or any S3-compatible storage (MinIO, Cloudflare R2 and similar).
Everything a reader needs to browse the analysis: each graph and its version snapshots, contracts, and issues. Salesforce credentials are never shared — only the results.
Open the folder's Settings and make the two choices at the top:
Sharing — pick S3.
Your role — pick Admin if you are the person refreshing graphs from the org and publishing the results, or Contributor if you are reading someone else's analysis. See Sharing and roles.
The S3 connection fields then appear:
Bucket — your S3 bucket name.
S3 folder — a folder inside the bucket that is the shared root. Leave it blank to use the whole bucket. Your local folder name does not have to match it — anyone pointing at the same bucket and S3 folder shares the same set.
Region, and an Access Key ID / Secret Access Key (plus an optional custom Endpoint for non-AWS storage).
Your secret key is encrypted in your operating system's keychain and is never written into the workspace. Use Test connection to confirm it works.
An Admin also needs a licence key, which Settings asks for in the same place. A Contributor does not.
Once configured, buttons appear on the folder header, next to New Graph:
Publish all — an Admin pushes results to S3.
Refresh all — a Contributor pulls the latest shared results down.
You only ever see one of the two. The person producing the analysis pushes, everyone else pulls, so nobody overwrites their own work.
If Publish all or Refresh all appears greyed out, hover it: the tooltip says what's missing, usually bucket details that haven't been filled in yet or a licence key that has expired.
Everyone can raise, comment on and close issues — including Contributors, who cannot refresh a graph from Salesforce. So issue lists are never simply copied over the top: publishing and refreshing both merge them, and an issue added on either side is kept. If two people give an issue the same number while apart, one of them is renumbered so neither is lost.
Contributors get an extra Publish issues button beside Refresh. It sends your issue additions, comments and closures back to the shared folder — issues only, nothing else. That means it also works with an access key that can write nothing but the issue list.
A shared bucket carries the names and email addresses of everyone in the org. You can scramble them before they leave, so the analysis can be shared without the people in it. See Hiding names and emails.
Roles inside Stood Flows decide which button you see, but the bucket itself should back that up. S3 access policies (Publisher & Reader) gives your bucket administrator two ready-made, IP-restricted access levels: one that can only push results in, and one that can only pull them down.