9 min
Share with your team
Hand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.
5,000 free credits to start.
- 01
Understand the four roles
A viewer reads the workflow and its runs. An operator can also start runs. An editor changes the prompt, model, and triggers. An admin manages sharing. Most teams end up with a few editors and everyone else as an operator.
- 02
Share with a person, a group, or everyone
Open Share on the workflow and pick a person, a group, a service account, or the whole organization. You can never grant a role above your own.
- 03
Set an expiry when it fits
A share can last forever, one day, one week, or a custom period. A contractor's access ends on its own. A trial run for another team cleans itself up.
- 04
Use groups and service accounts
Groups hold people and service accounts, so one share covers a team. A service account is a named identity a workflow runs as. It can be disabled without touching anyone's login.
- 05
Point everyone at the run history
Every run records the tool calls, the arguments, and the results. When someone asks why a workflow wrote that field or sent that message, the answer is a link.
- 06
Share a chat, and let people fork it
A chat can be shared by link up to a message you choose. Anyone with the link can fork it and continue from that point with their own copy. The original is untouched.
Keep going
Next guides
10 min
Run your first workflow
Describe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.
8 min
Use secrets and variables
Keep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.
10 min
Install and configure the Helios CLI
Install one binary, run `helios configure`, and go from an API key to a running workflow in your terminal. Every command prints JSON when piped.
Templates
Put it to work
Templates that use what this guide covers.
Engineering
Standup without the meeting
Reads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.
Support
Slack support triage
Watches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.
Operations
Weekly metrics report
Queries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.
Try it in your workspace.
Start free, connect a tool, and write the first prompt in plain words.