Once your agent works the way you want it to, you can share it with others. There are two ways to do this, and they have one key difference: whether other people use your agent running on your connected accounts, or get their own version running on theirs.
- Share with specific people gives specific teammates access to your agent. It keeps using your accounts.
- Publish to your company directory gives each person their own version. It uses their accounts, not yours.
What sharing gives access to
Your agent can see your data and take actions using the accounts you connected to it. When you share the agent, you also share those abilities.
Depending on what you connected, someone you share with can ask your agent to:
- Read your email and calendar, or send emails and create events
- Read or edit your docs
- Read and post in Slack, including channels and direct messages
- Use any other connector you added, with the permissions you granted it
Actions your agent takes appear under your name. If a teammate asks your shared agent to post in Slack, the message is sent by your account.
Important: Review the connectors on your agent before you share it.
Share with specific people
Give specific teammates access to the agent you built. They work with your agent, not a copy, so everyone stays on the same version, and the agent keeps using your connected accounts.
Choose how much each person can do:
| Access level | What it allows | Uses your connected accounts |
| View | See the agent’s setup and make a copy. | No. Their copy uses their own accounts. |
| Interact | Run the agent. | Yes |
| Full access | Change the agent’s setup, including its instructions and connectors; control the agent’s access and settings, including sharing it with others. | Yes |
Sharing works best when a handful of people need to work with the same agent, and when you are comfortable with each of them acting through your accounts. If someone only needs to see how the agent is built, choose View.
Publish to your company directory
List your agent in the company directory so anyone in your organization can find it and make their own version. Each person gets one of the following options:
- Install: Their version stays in sync with your original as you update it.
- Copy: Their own version to edit and adapt however they like.
Either way, the agent uses that person’s connected accounts. They connect their own Slack, email, and other apps before it can do anything, and their runs never touch your data.
Choosing between the different sharing options
| Preference | Selection |
| Let someone benefit from the setup you built | Publish or share with View so they can copy it |
| Let someone act on your behalf, using your data and accounts | Share with Use, Edit, or Manage |
| Keep a single agent that a small group works on together | Share with Edit or Manage |
Before you share
- Open the connector list and, for each one, ask whether you would share your login for that account with others.
- Remove connectors the agent does not need.
- If the others need what the agent does rather than access to your data, publish instead of sharing.
- If they only need to see how it is built, choose the View access.
What sharing does not do
- Instructions are not access controls. You can tell your agent in its instructions to use only certain channels or documents, and it will usually follow that. It is a guideline, not a boundary. The agent still holds full access to every connected account, and an unusual request can fall outside the scope you described. To keep data out of reach, remove the connector rather than writing a rule about it.
- Access is not scoped per source. You cannot share access to a single Slack channel or a single folder. Sharing an agent shares everything its connectors can reach.
- Access levels apply to sharing only. View, Use, Edit, and Manage apply when you share with specific people. The install-or-copy choice applies when you publish.