Contents
Guides
Share a workflow with your team
What you'll do: let teammates run (and optionally edit) one of your workflows, and know exactly what they can and can't do with it.
Your workflows start private — only you can see them. Sharing one adds people at a level you choose. You can change or remove someone any time; removal takes effect immediately.
The three levels
| Level | They can… | They can't… |
|---|---|---|
| Reader | Run the workflow, see its runs and reports | Change, share, or delete it |
| Editor | Everything a reader can, plus edit steps and schedules | Share it further or delete it |
| Owner | Everything, including sharing and deleting | — |
Steps
- Open the workflow's sharing. Open the workflow, then its share control, and add people by name or email at the level you want.
- Tell readers what to expect. A shared workflow appears in their list. When they run it, it runs with their identity in their isolated space — your files stay yours; only that workflow's folders are visible to the run.
- Remove someone when done. Take them off the list and their access stops right away — including scheduled runs they set up.
FAQs
Can shared people see my other workflows? No — sharing is per workflow. They see only the ones you shared with them.
Can they use my AI logins? They run with the accounts available to them — shared team logins, or their own. Logins you keep in your own store are never handed to someone else's run — but a connection you add to the workflow itself belongs to that place: everyone with access uses it, in chats and runs alike.
What about Code and Crews? Code is always private to its owner and can't be shared. Crews share like workflows: readers can ask, editors can change.
I removed someone — is it instant? Yes for anything new: opens, runs, and schedules are refused from that moment.