Share an agent

Every agent has an owner, the person who created it, and a list of access rules. Each rule gives someone View, Use or Edit access, and a rule can cover your whole organisation, a team, or one person. You set the rules in Manage access, which opens from the agent's settings in the builder.

Take John Martin, the operations director, who built Chase overdue invoices to find overdue invoices in BigChange and email a reminder for each. He wants the accounts team to run it whenever they need to, and Dylan Hughes to look after it. So the Accounts team gets Use, and Dylan gets Edit.

app.centrus.ai/app/agents/workflow-builder

Agents

Build modular AI workflows with reusable nodes

Chase overdue invoices

1,240 / 10,000 creditsValidateResetRunsSettingsUpdate & Publish

Chat Trigger

Tool: chase_overdue_invoices

Fetch unpaid invoices

List invoices

Overdue invoices only

Keep ALL of 2 rule(s)

Write reminder emails

GPT-5.6 Terra

Send reminders

1 action enabled

AI builderMap

Manage access

Owner:John Martin

1

People

Dylan Hughes

Edit

Teams

Accounts4 members

Use

2

Add access rule

ViewUseEdit

Organisation-wide

Add

3

1. 1The Owner. Whoever created the agent always has full Edit access, whatever the rules below say.
2. 2The rules: one person and one team, each with their own level.
3. 3Add access rule, where you share the agent with someone new.

• You are the owner or an admin. Only those two can change who an agent is shared with. Everyone else, including people with Edit access, cannot open Manage access.
• Your colleagues have Agent access. To find a shared agent on the Agents page and open it in the builder, a person needs Agent access switched on in Edit users. It is on unless an admin turns it off. See Open Agent Builder.
• The team exists, if you want to share with one. Admins set teams up in Settings. See Teams.

Running a shared agent from chat does not need Agent access, only Use or Edit access to that agent. So you can share an agent with someone who never builds anything.

1. 1Open the agent in the builder from Agents, using Open in builder.
2. 2Click Settings in the toolbar. The Agent settings window opens on its Agent tab.
3. 3Under Access, click Manage access. The settings close and the Manage access window opens in their place.

If you are neither the owner nor an admin, the Access row is not there at all. Ask the agent's owner, or an admin, to share it for you.

A new agent is private. Only its owner sees it in the Agents list, opens it in the builder or runs it from chat. Manage access shows only the owner, and reads Only you can access this workflow right now. Add a rule below to share it.

Manage access

Owner:John Martin

1

Only you can access this workflow right now. Add a rule below to share it.

2

Add access rule

ViewUseEdit

Organisation-wide

Add

3

1. 1The owner. This row never changes.
2. 2The note you see while nothing is shared.
3. 3A new rule starts on Edit for the whole organisation.

Add access rule starts on Edit and Organisation-wide. Clicking Add straight away lets everyone in your organisation change, publish and delete the agent. Pick the level and the people first.

Being an admin does not show you a colleague's private agent. Admins can manage the access of any agent they can open, but an agent that nobody has shared with them stays out of their list.

Each level includes everything in the one below it. The info icon beside Manage access describes them:

• View: can see the agent, read-only in the builder, and find it in lists. Cannot run it from chat or change it.
• Use: View, plus can run it from chat and ask Centrus about its runs or whether its connections are working.
• Edit: Use, plus can change it, in the builder or by asking for changes from chat.

View and Use look the same in the builder. The difference is chat: someone with View cannot run the agent from the Chat page, WhatsApp or Teams, and Centrus does not offer it to them. Run an agent from chat and WhatsApp covers running from chat.

Someone with Use can still start a run without Edit. Run now is hidden in their builder, but if your organisation has Agent Builder chat tools switched on, they can ask Centrus on the Chat page to run the agent, and it runs as if they had clicked Run now.

Sharing with a team keeps access in step with the team. Someone who joins Accounts gets the agent straight away, and someone who leaves loses it.

1. 1In Add access rule, click the level the team should have. For the accounts team that is Use.
2. 2In the box that reads Organisation-wide, choose Specific team.
3. 3Click Choose a team and pick the team. You can type to search.
4. 4Click Add. Access updated appears, and the team is listed under Teams.

Manage access

Owner:John Martin

Only you can access this workflow right now. Add a rule below to share it.

Add access rule

ViewUseEdit1

Specific team2

Accounts3

Accounts

Contracts

Engineers

Office

Add4

1. 1The level: View, Use or Edit.
2. 2Who the rule covers: Specific user, Specific team or Organisation-wide.
3. 3The team, from Choose a team.
4. 4Add saves the rule. It stays grey until you have picked someone.

Only admins see the list of teams. If you own an agent but are not an admin, Choose a team has nothing in it. Share with the people one at a time, ask an admin to add the team, or ask the AI builder to share it with the team by name, as shown in Share by asking the AI builder below.

1. 1In Add access rule, click the level. Dylan Hughes looks after the agent, so he gets Edit.
2. 2Choose Specific user, then pick the person from Choose a person. The list leaves out the owner and anyone who already has their own rule.
3. 3Click Add.

To share with everyone, leave the box on Organisation-wide, pick the level and click Add. An Organisation row appears at the top of the rules, and Organisation-wide is greyed out in the box until you remove that row.

Access updated1

Manage access

Owner:John Martin

People

Dylan Hughes

Edit

Teams

Accounts4 members2

Use

Sarah Price via AccountsPriya Shah via AccountsTom Walsh via AccountsGrace Okafor via Accounts

Add access rule

ViewUseEdit

Organisation-wide

Add

1. 1Access updated confirms the rule is saved. It applies at once, with no need to save or publish the agent.
2. 2Click a team's name to see who has access through it.

Once you add a rule, the box goes back to Edit and Organisation-wide. Check it again before you add the next one.

Each rule has its own level box and an X. Pick a new level from the box to change it, or click X to remove the rule. Both apply as soon as you click, with no confirmation, and Access updated appears.

Manage access

Owner:John Martin

OrganisationEveryone in your organisation

View

People

Dylan Hughes

Edit1

2

View

Use

Edit

Teams

Accounts4 members

Use

1. 1The level box. Pick View, Use or Edit.
2. 2X removes the rule.

• The highest level wins. In the example, everyone has View through the Organisation rule, the accounts team has Use, and Dylan has Edit. Each person gets the highest level any rule gives them.
• Removing a team takes away the access its members had through it. A member who also has their own rule, or the Organisation rule, keeps that.
• Removing every rule makes the agent private again.
• Ownership cannot be transferred. The person who created an agent stays its owner. If they leave, an admin can still manage its access, and someone with Edit can keep it running, or duplicate it to have a copy of their own.

Once the agent is shared, it appears in your colleagues' Agents list. Sarah Price from the accounts team opens it with Open in builder and sees View only in the toolbar. She can read every step, but cannot move, add or change them, and the AI builder is closed. Hover over the list of nodes and it reads You have view-only access to this agent.

With View or Use, the Runs panel still lists every run, opens each one step by step, and shows earlier versions under Version history. Approving or rejecting a waiting run in the builder needs Edit. See Conditions, loops and approvals.

The owner and admins can open Manage access. An admin who has only View or Use on an agent still sees the Access row and can share it, but reads You have view-only access to this agent. beside the button, and needs Edit to change, publish or run it.

The same two people also set the agent's Integration mode and Per-run credit budget in Agent settings. Someone with Edit who is not the owner or an admin does not see those rows. Automation credits and usage limits covers the budget.

Sharing an agent never shares anyone's sign-in details. The accounts the agent is connected to stay on the agent, and nobody you share it with can see or copy them. What changes is whose account a colleague's run uses, which Integration mode decides:

• Agent-level, the default. Every run uses the agent's own connections, whoever starts it. When Sarah runs Chase overdue invoices from chat, the reminders go from the Outlook account connected to the agent.
• Per-user. Outlook and Gmail steps use the account of whoever started the run instead, connected on their own Integrations page. Each person needs that account connected, and the step's Connection box lets them check whether theirs is.

Per-user mode only suits agents whose connected steps are all Outlook or Gmail. In Per-user mode, Outlook steps can only send emails and create drafts, and Gmail steps can send, read and draft. Any other connected step, such as BigChange or Excel, stops the run with an error. Per-user is also only available for agents that start from chat or Run now, because a scheduled run has nobody to borrow an account from. The example agent fetches invoices from BigChange, so it stays on Agent-level.

When you connect an account on a step, Copy from existing agent only lists agents you created. You cannot copy a connection from an agent that was shared with you.

As the owner or an admin, you can also ask the AI builder to share the agent. Save the agent first. Ask in your own words, and give an email address when you mean one person. Centrus repeats back exactly what it will change and waits for you to say yes before doing anything.

Chase overdue invoices

1,240 / 10,000 creditsValidateRunsSettingsUpdate & Publish

Chat Trigger

Tool: chase_overdue_invoices

Fetch unpaid invoices

List invoices

Overdue invoices only

Keep ALL of 2 rule(s)

Write reminder emails

GPT-5.6 Terra

Send reminders

1 action enabled

AI Agent Builder

Edits apply live on the canvas

John Martin · 10:02

Share this agent with the Accounts team so they can run it, and give dylan.hughes@meridianfm.co.uk edit access.

Centrus Agent Builder · 10:02

Before I change anything, here is what I will do on Chase overdue invoices: give the Accounts team Use access, and give Dylan Hughes Edit access. Both take effect straight away, separately from your unsaved canvas changes. Shall I go ahead?

1

Yes, go ahead

MinimiseMap

1. 1Centrus restates the change and waits. Nothing is shared until you confirm.

Sharing this way takes effect as soon as you confirm, like Manage access. It is not part of the canvas, so Discard does not undo it. If two teams have similar names, Centrus asks which one you mean.

When you message Centrus on the Chat page, WhatsApp or Teams instead, only the agent's owner can change who it is shared with. Admins make those changes in the builder. Build and edit agents from chat and WhatsApp covers working on agents by message.

If a colleague wants their own version to change freely, duplicate the agent instead. With Edit access, open Settings and click Duplicate this agent at the bottom of the Agent tab.

• The copy is yours. You become its owner, and it starts private, whatever the original was shared with.
• It starts as a draft, with the same steps. A Chat Trigger's tool name gets a number added, so the two do not clash in chat.
• Connections are not copied. Connect the accounts again on the copy before you publish it.

Save any changes first: the button is greyed out with Save the draft first. while the agent has unsaved changes. Then share the copy with your colleague at Edit, or let them duplicate it themselves if they already have Edit.

Manage access works the same on a phone. The window fills the width of the screen and the Add access rule controls wrap, one under another.

09:41

Centrus

Agents

Build modular AI workflows with reusable nodes

Chase overdue invoices

Update & Publish

Chat Trigger

Tool: chase_overdue_invoices

Fetch unpaid invoices

List invoices

Overdue invoices only

Keep ALL of 2 rule(s)

Write reminder emails

GPT-5.6 Terra

Send reminders

1 action enabled

Manage access

Owner:John Martin

Teams

Accounts4 members

Use

Add access rule

ViewUseEdit

Specific user

Dylan Hughes

Add

The rule wraps onto four lines

The View only label is hidden from the toolbar on a phone. Someone with View or Use still cannot change anything, but nothing on screen says why.

Restoring an earlier version leaves the sharing as it is. See Publish, pause and restore versions.