9 min read
Share with your team
Hand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record of what happened.
- 01
Understand the three roles
An admin manages the organization, its members, and its connections. An editor changes a workflow's prompt, model, and triggers. A user runs a workflow and reads its results. Most teams end up with a handful of editors and everyone else as a user.
- 02
Set visibility on the workflow
A restricted workflow is visible only to the people you grant access. An organization workflow is visible to everyone in the org. Start restricted while a task is still finding its shape, then open it up once the output is worth reading.
- 03
Bring your identity provider
SAML and OIDC single sign-on put access under the same control as the rest of your stack, and SCIM provisioning means a person who leaves the directory loses their agents with them. Admins configure both from the organization settings.
- 04
Let people run what they cannot edit
The two-sided arrangement is the point: give the whole team the user role so anyone can hand a task to an agent, and keep the prompt, the credentials, and the triggers with the people responsible for them.
- 05
Point everyone at the run history
Every run records the tool calls the agent made, the arguments, and the results. When someone asks why an agent wrote that field or sent that message, the answer is a link rather than a conversation.
- 06
Share a chat, and let people fork it
A chat can be shared by link, up to whichever message you choose, so the half you were still thinking out loud in stays yours. Anyone can fork the shared chat to keep going from that point with their own copy of the conversation and its files, and the original is untouched.
Keep going
Next in the track
10 min
Run your first agent
Describe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run 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, and both are scoped to the level where they belong.
12 min
React to GitHub events
Start an agent the moment a pull request opens, a build goes red, or a tag lands — filtered down to exactly the events you want it on.
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 so nobody has to attend one.
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 anomalies called out.
Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.