Skip to main content
There is one verb, share. Dashboards, chats and skills all share the same way. Open the object’s Settings → Sharing. Three audiences, stacked.

​
General access

This row is the web audience alone, and it has two states.
  • Restricted, meaning only people with access can open it.
  • Anyone with the link, a read-only link that needs no account.
A link viewer sees the current published baseline with a data as of stamp, so staleness stays honest. They get no filters, no chat, and no refresh, because the public page has no controls at all. Their visit does count, which keeps a running refresh schedule alive, though it will not revive a paused one (Refresh).
A workspace admin can turn external links off for the whole workspace. When they have, the option is visibly unavailable rather than silently missing.
To change a link’s URL, switch to Restricted and back. That revokes the old token and mints a new one. Creating again while a link is live hands back the same URL rather than a second one.

​
Naming people

Search for a colleague and add them. The + grants one step up from the workspace baseline, and you change the role from the select on their row afterwards. Roles differ by object kind. A dashboard grant can be Viewer or Editor. A chat grant is Viewer only, since there is one writer per conversation. Guests are always Viewer, whatever the menu would otherwise offer. The owner sits at the top with no role menu. Ownership moves through Change owner, and only to a named collaborator. See Dashboards for why the owner matters beyond attribution.

​
Sharing with someone outside the workspace

Invite them by email from a dashboard’s Sharing pane. This is the one object kind that takes outside invitations; on a chat or a skill, typing an unknown address finds nobody. They become a guest, holding only what was explicitly shared with them, always read-only. Until they accept, their row reads PENDING, and you can resend or withdraw. A guest can be made a full member later from Settings → Members → Make member. Editing is a capability of membership, not something a guest grant can carry.
A chat link does not hand over the files. Attachment chips carry the name and kind, never the bytes or the extracted text. Inside the app it is different, since anyone who can read the thread can open its files. See Attachments.

​
Requesting access

Landing on a dashboard you cannot open gives you a way to ask for edit access, which notifies the people who can grant it. While your request is outstanding you see that it is pending rather than being able to ask repeatedly. Guests get no request button. A guest’s access is defined entirely by what was shared with them, so a request that could only be refused is not offered.

​
What sharing never does

There is no peer-to-peer editing. Editing means membership in the owning workspace plus edit permission on the object. You cannot grant someone outside your workspace the ability to change your dashboard, and the sharing screen says so rather than offering an option that would not work.