Sharing an AI employee with a teammate: view, edit and who owns it
An AI employee one person built often serves a whole team. How to share it to view or to edit, with people or groups, what personal accounts change, and handing it over.
Part of the guide AI employees
To share an AI employee with a teammate, open it in the editor, press Share, and choose who sees it and what they may do: keep it private, let your whole team view it, let your whole team edit it, or add named people or groups, each with view or edit. Viewers see the flow, its runs and everything it found; editors can also change it. Two things set limits on sharing: a flow that signs in with your own personal account can only be changed and run by you, and people outside your organization can only ever view.
This article is for anyone who built an AI employee that colleagues now depend on, and for team leads setting up how a group works with several. It covers the choices in the Share window, when to give edit rights, what personal accounts change, how to hand an employee over, and habits that keep a shared employee from breaking.
The choices in the Share window
- Private. Only you, and anyone you add by name, can see it. Organization admins can still pause or delete it.
- Team can view. Everyone in your organization sees the flow, its runs, its results, maps and reports, and can ask about it in the Team inbox. Nobody but you and the editors you name can change it.
- Team can edit. Everyone who is not a viewer in your organization can change the flow.
- Named people or groups. On top of any of the three, share with a person or a group, each with view or edit. A team made on the Team page is also a sharing group: share with the Sales team, and whoever joins it later sees the employee too.
Results follow the flow. If a colleague can see an employee, they can see what it found in Results, on the map and in its reports; if they cannot, its results stay out of their lists too.
View or edit: which to give
Most people who rely on an AI employee need to see what it found, not change how it works. Give view by default and edit to the few who will look after it.
| Teammate | Usually needs | Why |
|---|---|---|
| A rep who works the leads it finds | View | They read results and ask the employee questions; a change by mistake would affect everyone. |
| A second owner who covers your holidays | Edit | Someone has to fix it when a block fails and you are away. |
| A manager who reviews the weekly report | View | Reports, maps and runs are all visible to viewers. |
| A colleague who is improving the scoring | Edit, for a while | Give edit for the work, then set them back to view. |
A starting point; your team may divide the work differently.
Roles on the Team page add a second layer. A viewer sees everything and changes nothing, whatever a flow's sharing says. A custom role can let someone edit flows but not deploy them, send for real, make public links, add connections or delete, so an editor can improve an employee without being able to switch on sending to customers.
What personal accounts change
AI employees often send through an app account: a Slack workspace, a Google Sheets file, an email inbox. A connection can be a team connection, which any flow in the organization may use, or a personal one, which only flows owned by the person who added it may use.
- A flow that uses its owner's personal connection can be changed, run and deployed by its owner only. Others with edit rights can look but not change it, so the owner's account is never used by someone else.
- A private flow that uses its owner's personal connection is seen by its owner only. Admins can pause or delete it without opening it.
- Nobody can put someone else's personal connection into their own flow.
Working on one employee together
Two people can have the same flow open: each sees the other's cursor and selected blocks, and changes appear on both screens as they are made. Comments can be pinned to a block, so a question about the scoring sits on the xMap LLM block rather than in a chat elsewhere. Every save is kept in the version history, and What changed shows, in plain words, what a colleague altered and lets you restore an earlier version.
Handing an employee over
When someone changes role or leaves, their AI employees should not stop. An organization admin can change a flow's owner on the flow; the new owner then answers for it, and it uses their personal connections from then on, so check which accounts it needs. When a person is removed from the organization, their flows pass to the admin who removed them (or the first admin), shares made with them end, and their personal connections in that organization are deleted, so any employee that used one needs a new account before its next run.
A made-up example: one employee, four people
Say a recruiting firm in Johannesburg has an AI employee that finds companies hiring warehouse staff every morning and posts them to a Slack channel. Nadia built it. She shares it with the Recruiters group to view, so the six recruiters see each morning's list and ask the employee follow-up questions in the Team inbox. She gives Thabo edit, because he covers for her. And because the Slack message used her personal Slack sign-in, she asks the admin for a team Slack connection and switches the employee to it, so Thabo can fix it on his own. When Nadia moves to the Cape Town office, the admin makes Thabo the owner; nothing stops running.
Habits that keep a shared employee healthy
- Give it a clear name, so the team knows which employee does what.
- Share to view by default; give edit to one or two named people.
- Use team connections for anything more than one person will look after.
- Before a big change, run it as a test (nothing is sent) and leave a comment on what you changed.
- Let the employee ask before it sends anything outside the team, with an Approval step, while new editors learn it.
Any template, such as New places every morning, only new or Morning call list with decision makers and call notes, makes an employee you can share the same way once it is yours.
Questions
Can someone with view rights change the employee?
No. They see the flow, its runs, results, maps and reports, and can ask about it, but changing its blocks needs edit rights. Anyone with the Viewer role changes nothing anywhere.
Why can my colleague not edit a flow I shared to edit?
If the flow uses your personal connection, only you can change, run or deploy it. Switch it to a team connection, or make your colleague the owner.
Can I share an employee with someone at another company?
Yes, to view only, and they must meet your organization's security rules. For clients without an account, use a client view or a public link instead.
What happens to my employees if I leave the company?
They pass to an admin, shares made with you end and your personal connections in that organization are deleted, so the new owner reconnects any account they used.
Does sharing an employee share its results?
Yes. Results, maps and reports follow the flow, so whoever can see the employee can see what it found.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates