Display.dev uses organization roles for administration. Roles decide who can manage the organization; visibility decides the normal audience for each artifact.
Roles
- Owner — full organization administration, including billing, members, settings, branding, API keys, and artifacts.
- Admin — organization administration without ownership transfer. Admins can manage billing, members, settings, branding, API keys, and artifacts.
- Member — publish and view artifacts according to each artifact's visibility and sharing settings.
Keep owner and admin roles limited to people who are allowed to administer the organization. For separate administrative boundaries, use separate organizations.
Artifacts
Owners and admins have administrative access to organization settings and to non-private artifact administration in their organization. This supports normal operations such as fixing access settings, renaming or deleting obsolete public or company artifacts, and handling offboarding.
Private artifacts have a stricter owner boundary. The artifact creator and the organization owner can manage a private artifact's access and lifecycle. Admins can open a private artifact's metadata view, but they cannot change its sharing settings, add themselves to sharedWith, rename it, update it, roll it back, or delete it unless they are also the artifact creator. Owners and admins can view or export private artifact content only when they are the publisher or their email is explicitly listed in sharedWith.