Most of what you build in Dema — agents, skills, apps, dashboards, reports, and sessions — starts out private to you and stays that way until you choose to share it. This page explains how that sharing works, what each visibility level means, and what Dema shows you before you change who can see something.
How access works in Dema
Three things decide what a person can see and do:
| Layer | What it controls | Where to manage it |
|---|
| Role | Organization-wide capabilities (Admin, Member, Guest) | Manage users |
| Teams | Which metrics, dimensions, and reports a group can see | Creating and managing teams |
| Sharing | Who can see and use a specific agent, skill, app, or session | This page |
Visibility levels
Every resource you create in Dema — agents, skills, apps, dashboards, reports — has a visibility setting that controls who can see and use it:
| Visibility | Who can see and use it |
|---|
| Private | Only you |
| Team | You and everyone on the selected team(s) |
| Organization | Everyone in your organization |
What happens when you share
Before a sharing change takes effect, Dema shows you what it will expose, so there are no surprises. Sharing something more widely can also make the things it depends on reachable by the new audience — Dema spells that out before you confirm, and lets you apply it in one step.
What happens when you make something private
Narrowing a resource’s visibility — making it private, or limiting it to fewer teams — is just as transparent. Dema shows you what will lose access before you confirm.
If something was reachable only because this resource was shared more widely, that connection is removed when you confirm, so “private” really means private. You, the owner, always keep access.
Making something more private can cut off people who were reaching it indirectly — for example, through another resource you’d shared with a wider audience. Review the summary Dema shows you before confirming.
How this works in practice
The rules above apply to everything you create. For how they play out with the Dema Agent — the skills and apps a shared agent brings along, and who can see and continue your sessions — see Sharing agents and sessions.
Best practices
- Share at the broadest level the work actually needs, and let the pieces it depends on stay private — they stay reachable through what you shared.
- Always read the summary Dema shows you before confirming a sharing change, especially when making something private.
- Use teams to share with a focused group rather than your whole organization when only some people need access.
