Skip to content

Sharing and access

Choose who can open an artifact and invite specific people by email.

On this page

Choose an audience for each artifact: anyone, organization members, or only the artifact creator and invited people.

The three audiences

  • Public – anyone can open the artifact, with no sign-in required.
  • Company – organization members can view after signing in.
  • Private – the artifact creator and invited people can view after signing in.

Invited people outside your organization do not need a Display.dev account. They enter the invited email address and a one-time password (a six-digit code sent to that address) when they first open the artifact.

Access matrix

PersonPublicCompanyPrivate
AnyoneViewSign inSign in
Organization memberViewViewOnly when creator or invited
Invited person outside the organizationViewView after email codeView after email code
Person who is not invitedViewNo accessNo access

When access is denied, Display.dev does not reveal whether the artifact exists.

Update your profile

Open Settings → Profile to change your name or profile photo. Upload a JPEG, PNG, or WebP photo and adjust its crop, use a photo from a connected Google or Microsoft account, or remove your current photo. Then save your profile.

See who else is viewing

When you open an owned artifact while signed in, the header shows other signed-in people who currently have that artifact open. Members appear with their Display.dev profile photo when they have one. Invited people and members without a photo appear by initial.

Hover over or keyboard-focus a photo or initial to see the person's name. Select it to see everyone viewing. When the header shows a +N count, select it to see names and viewed versions for up to 20 people. If more people are viewing, the list shows how many others are there. Invited people outside the organization are labeled Guest; their full email address is not shown. The list updates while the tab is visible.

Anonymous visitors never appear, even on public artifacts. Your own avatar is not shown. Display.dev removes inactive viewers shortly after their last update, and hides the viewer list if presence is unavailable.

An artifact that is already open can show your previous profile name or photo for up to one hour. After that, refresh the artifact to show your current profile.

Presence follows the artifact's audience. It does not let anyone see an artifact or a viewer list they could not already open.

Invite people

Invited email addresses extend the audience of company and private artifacts:

  • For a company artifact, organization members already have access. Invite people outside the organization when they also need access.
  • For a private artifact, invite each organization member or outside person who needs access.
  • For a public artifact, invitations do not change access because anyone can already open it.

The API field for invited email addresses is named sharedWith. You may see that name in structured CLI or MCP output.

Plan requirements

Public, Company, and Private are available on every plan. On Free, Company and Private artifacts share the limit of 10 gated artifacts.

User-scoped publishes default to Private. Organization-scoped service publishes default to Company. Anonymous publishes are Public.

See Plans and limits for current limits.

Anonymous publishes

An anonymous publish starts as public and stays public after it is claimed. Claiming transfers ownership but does not change the audience.

After claiming, the artifact creator can change its audience from the artifact detail page or with dsp share.

Change the audience

When the artifact creator opens Share from the artifact header, the menu lists every specifically invited email address. Manage access closes that menu and opens a focused access sheet in a popup – without the rest of the dashboard – so the artifact stays open for reference. After a successful save, the sheet briefly shows Saved, then closes. Reopen Share to see the current visibility and invited people without reloading the artifact.

If you belong to more than one organization, the access sheet opens in the artifact's organization.

The creator can also use the access controls on the artifact detail page or run:

bash
dsp share <shortId> --visibility public
dsp share <shortId> --visibility private --add-users alice@partner.com
dsp share <shortId> --remove-users bob@partner.com

The command prints the updated visibility and invited people when the change succeeds.

Was this page helpful?