Who owns an agent
The person who created an agent is its owner. On the Agents home page, the Shared tab shows Owned by under the name of your 3 most recently active shared agents. The full list of shared agents doesn't show the owner. If you can share the agent, the owner is also listed first under People with access in the share dialog.
Only the owner can delete an agent. Other people may see Delete agent in the agent's ⋮ menu, but they get an error if they try. There is no way to change an agent's owner today.
Share an agent
Go to Agents, click View all my agents, and find the agent.
Click ⋮ in the Actions column and choose Share. If you don't see Share, you don't have permission to share that agent.
Under Add people, search by name or email, pick a role, and click the add button.
To change someone's role or remove them, use the controls next to their name under People with access.
Changes apply as soon as you make them. There is no Save button.
Roles:
View and Use: they can run the agent but not change it.
Edit, View, and Use: they can run it, change it, and share it with others.
If you share with someone outside your Coworker workspace by email, they can only get View and Use.
People you share with see the agent on their Shared tab.
Share with your whole company
In the share dialog, under Organizational access, choose:
No organizational access (default)
View and Use: everyone at your company with a Coworker account can run it
Edit, View, and Use: everyone can run, change and share it
Everyone else at your company then sees the agent on their Shared tab.
Org-wide access does not give each person their own copy, and it does not give them the schedule. Read the next section before sharing a scheduled agent.
What happens to a shared agent's schedule
Scheduled and triggered runs (on a schedule, from a Slack event, a meeting, a custom event or a real-time trigger) always run as the owner, with the owner's data access. Sharing the agent does not create a schedule for anyone else, and results go wherever the owner set them to go.
When someone runs a shared agent themselves, in the app or by mentioning it in Slack, it runs as them, with their own access and their own credits.
So if each teammate needs the agent to run on their own schedule with their own data, each of them should make a copy (below).
Make your own copy with Duplicate
Go to Agents, click View all my agents, and find the agent on My Agents or Shared.
Click ⋮ in the Actions column and choose Duplicate.
The builder opens with everything filled in and the name starting with [Copy].
Check where the results go. Email recipients and Slack channels are copied from the original, so update them to your own.
Save. The copy is yours, shows on your My Agents tab, and isn't shared with anyone.
The schedule is copied. Real-time triggers are not, so set those up again on your copy if the original used one.
When an editor changes someone else's agent
If anyone other than the owner changes an agent (its instructions, tools, triggers and so on), its scheduled and triggered runs pause until the owner approves. This stops an agent running as the owner on changes the owner hasn't seen.
The owner sees a Needs review badge on the agent, and a banner in the builder with an Approve button. After approving, scheduled and triggered runs resume.
Everyone else sees "Waiting for [owner] to approve recent changes; scheduled and triggered runs are paused."
Running the agent yourself still works while it waits.
Personal MCP servers
If an agent uses an MCP server the owner connected for themselves, those tools only work when the owner runs it. The share dialog warns about this. To make the tools work for everyone, ask an admin to add the server as a workspace MCP server.
FAQ
Can an admin push one agent to every user as their own agent? Not in one step. Org-wide access lets everyone run the same agent, but scheduled runs still run only as the owner. For each person to have their own scheduled version, each person uses Duplicate.
Can people I gave edit access reshare the agent? Yes. Anyone with Edit, View, and Use can add or remove people and change organizational access.
Who pays the credits? Runs someone starts themselves use their own credits. That includes @-mentioning the agent in Slack, which runs as the person who mentioned it. Scheduled runs, and runs started by an event trigger, run as the owner and use the owner's credits.