Skip to main content
See Access and sharing for the rules that apply across Dema. This page explains what happens when you share an agent or one of its sessions.

​
What people can use through a shared agent

Anyone you share an agent with can use its skills and apps through that agent, including private ones. Those private skills and apps do not appear in anyone else’s library. Other people cannot open or edit them directly.
Your Pricing analyst agent uses a private skill called margin-calc. If you share the agent with the Growth team, the team can run the agent and it can use margin-calc for them. The skill stays private and belongs to you.
The diagram shows what the Growth team can access after you share the agent: Access flow after sharing an agent: the Growth team can use the shared agent and read its sessions, while the private skill, private app, and your connected accounts are reachable only through the agent Access flow after sharing an agent: the Growth team can use the shared agent and read its sessions, while the private skill, private app, and your connected accounts are reachable only through the agent The shared agent is the only path to the items on the right. If you stop sharing the agent, the team loses that access. The items still belong to you.

​
Connected accounts

People who use a shared agent can also use its integrations, such as Slack, Gmail, or Shopify. These integrations use the accounts connected to the agent. Before you share an agent more widely, Dema lists the connections and resources that its new audience will be able to use.
Review this list before you confirm. For example, people who use an agent connected to Gmail may be able to read or send email from that account, depending on its tool permissions.

​
Linking apps and skills to an agent

Linking an app or skill to an agent does not change the item’s visibility. However, everyone who can use the agent can use the linked item through it. If a link gives more people access, Dema shows who gains access and how to remove it before you confirm.

​
Making things private again

What happens depends on the new visibility:
  • Specific teams: Links stay in place. Dema lists the agents that can still use the skill or app.
  • Private: Dema removes the skill or app from agents with a wider audience. People who used it through those agents lose access. You keep access as the owner.
Making an agent private removes access for everyone else who could use it. Dema shows the effect before you confirm.

​
Transfer ownership

The owner of an agent or app can hand it over to another member of your organization from the Owner row on the agent’s Configuration page or the app’s details panel. Only the current owner can do this. Before you confirm, Dema shows an impact preview:
  • Routines that move with the agent. Any routine you own on the agent transfers to the new owner. It keeps its schedule and stays active. Its next runs will fail on any connected accounts the new owner has not reconnected yet.
  • Linked skills and apps. Skills and apps you own that are linked to the agent are listed as candidates to transfer alongside it. Everything is ticked by default; untick the ones you want to keep. Anything left unticked stays with you, and other agents that link to it are unaffected.
  • Connected accounts to reconnect. Integrations you connected to the agent are switched off during the transfer. The new owner needs to reconnect each listed toolkit before the agent can use it again.
  • Loss of access. If the agent or app is private, you lose access to it once the transfer completes. Share it with a team you belong to before transferring if you want to keep viewing it.
Read the list of connections to reconnect before you confirm. Once the transfer commits, neither you nor the new owner can see the previous owner’s connections, so you cannot look them up afterwards.

​
Who can see an agent’s sessions

Anyone who can use an agent can open and read its sessions, including scheduled runs. Sessions owned by someone else are read-only. You can read the messages and download files, but you cannot send messages, rename the session, or delete it. You can also share one conversation directly. Share conversation makes it available by URL to everyone in your organization, including people without access to the agent. A conversation is either private or shared with the whole organization. You can make it private again.