Sharing in Dema follows a few simple rules that apply to everything you create — see Access and sharing for visibility levels and the general model. This page covers what’s specific to agents: what comes along when you share one, and who can see and continue the sessions run on it.
Sharing an agent shares what it uses
This is the most important idea to understand: anyone you share an agent with can use its skills and apps — including the private ones — through that agent.
An agent often depends on private skills and apps you’ve built. When you share the agent with a team or your whole organization, those people can use everything it relies on through the agent — even though the skills and apps themselves stay private and don’t show up in anyone else’s library.
Example. You own an agent called Pricing analyst that uses a private skill, margin-calc. You share Pricing analyst with the Growth team. The team can now run the agent, and the agent uses margin-calc on their behalf. The skill stays yours and stays private — Growth never sees it in their own skills list, and can only reach it through the agent you shared.
This keeps sharing simple: you share at the agent level, and the pieces it needs come along for the ride without you having to share each one separately. The things you reference stay yours, and they’re only reachable through the agent you chose to share.
Linking apps and skills to an agent
Linking an app or skill to an agent doesn’t change its visibility. It stays exactly as private as it was — linking simply lets the agent use it. As described above, anyone who can use the agent can then use that app or skill through the agent, even while it stays private and out of everyone else’s library.
When you link something, Dema shows you who will be able to reach it through the agent, so the exposure is never a surprise. Nothing is made public on your behalf.
If you later reduce a linked app or skill’s visibility down to Private — for example, from Team to Private — it’s removed from any agent that’s shared more widely, so the agent can no longer use it and people who reached it through that agent lose access. You, the owner, keep it. (Reducing it to a smaller set of teams instead — rather than all the way to Private — keeps the link; Dema just shows you the resource is still reachable through those agents.)
Sessions and agent access
A session runs on an agent, and access to a session follows access to its agent. Anyone who can use an agent can open and continue the sessions run on it — so a session built on an agent you’ve shared with a team is visible to that team, even if you never shared the session itself.
Sharing a session goes one step further: it opens the session to everyone in your organization, including people who don’t have access to its agent.
The person who started a session can always open, rename, and delete it. But continuing a session — sending a new message — runs the agent, so it’s allowed only while you still have access to that agent. If the agent is unshared from you or deleted, you can still open your own session to read it, but you can’t continue it. 
