Agents, skills, apps, dashboards, reports, and sessions start out private. You decide when to share them and with whom.
How access works in Dema
Access depends on roles, teams, and the visibility of each resource:
Roles and teams set organization-wide access. Visibility controls access to a specific resource.
Visibility levels
Each agent, skill, app, dashboard, and report has a visibility setting:
Sessions are either Private or Shared with your organization. A session also follows the visibility of its agent. See Sharing agents and sessions for details.
The person who creates a resource owns it. Sharing changes who can use the resource, not who owns it. For agents, skills, and apps, only the owner can change its visibility, rename it, or delete it.
What happens when you share
Before you share a resource, Dema shows who will gain access. It also lists any linked resources that the new audience will be able to use.
What happens when you make something private
Before you make a resource private or limit it to fewer teams, Dema shows who will lose access.
If another resource provides indirect access, Dema may remove that link when you confirm. You keep access as the owner.
Making a resource more private can also remove indirect access through a resource shared with a wider audience. Review the summary before you confirm.
Agents and sessions
See Sharing agents and sessions to learn how a shared agent provides access to its skills, apps, integrations, and sessions.
Share with the smallest audience that needs access. Use teams when only part of your organization needs a resource, and review the access summary before you confirm a change.
