Sharing artifacts¶
An artifact is only useful once it reaches the right people. You can share any artifact three ways: invite specific teammates with a role, open it to everyone in the workspace, or publish a link. All three are managed from the artifact’s share panel.
Prerequisites¶
Editor role to share or publish. The person you share with needs whatever access the method you choose implies, see below.
Two roles¶
When you share with a named person, you choose what they can do:
Read only: They can open and use the artifact, read a report, filter a data app, but not change it
Collaborator: They can edit too, working on the same live artifact; their changes create new versions like yours do
A share invitation moves through three states: pending once sent, accepted once the recipient takes it up, and revoked if you withdraw it. Revoking removes their access immediately.
General access¶
The General access setting in the share panel decides who can open the artifact beyond the people you invite by name:
Option |
Who can open it |
|---|---|
Restricted |
Only invited people can open this artifact |
Everyone in workspace name |
Everyone in the workspace can view |
Anyone with the link |
Anyone on the internet with the link can view |
Pick an option and click Share to apply it. Named shares keep working whichever option you choose.
The artifact’s badge in the list and on its detail page shows its broadest reach: Public when a public link exists, Workspace when everyone in the workspace can view, Shared when it is shared with specific people, and Draft otherwise. The Status filter on the artifacts list uses the same four values.
Note
Workspace access is view-only. Everyone in the workspace can open the artifact, but only you and named collaborators can edit it, and it does not let them change its sharing or delete it.
Public links¶
Setting General access to Anyone with the link mints a shareable link that anyone with the URL can open, useful for stakeholders who do not have an Adverity Atlas account. The link appears after saving.
A link, not a login: Recipients open the artifact without signing in
Expires by default: Links last 30 days unless you set a different lifetime; they do not live forever by accident
Revocable any time: Kill a link before it expires and the URL stops working immediately
Switching General access away from Anyone with the link, to Restricted or to the workspace, revokes the link: the panel warns “The existing link will stop working after saving.” Switching back later issues a new link rather than reviving the old one.
Every public link across the tenant is listed under Settings > Data Governance > Public Shares, where an admin can review and revoke them, so a link shared more widely than intended can always be found and pulled. See Data governance.
Warning
A public link is reachable by anyone who has the URL, with no sign-in. Publish only what is safe to share that way, prefer a named read-only or collaborator share for internal work, and revoke links you no longer need.
How a public data app runs its queries¶
A data app runs live queries, and a visitor arriving on a public link has no Adverity Atlas account to run them as. So a published data app queries as a service account that Adverity Atlas provisions for it automatically when you publish. There is nothing to choose and nothing to set up, and re-publishing reuses the same account rather than creating another.
The account appears in Settings > Service Accounts, named after the artifact and marked as managed by Adverity Atlas. It holds no permissions and has no API key: the public query broker supplies its own read-only capability rather than reading the account’s, so the account is an identity to attribute the queries to, not a grant.
That makes it a kill-switch. Deactivate the account and every public link running as it stops serving data from the next request onwards, independently of when the link itself expires.
Note
The account cannot be deleted while a link is bound to it. Adverity Atlas refuses with “A shared data app loads its data as this service account. Deactivate it instead, or stop sharing that app publicly first.”
Choosing how to share¶
Situation |
Share method |
|---|---|
A teammate should help build it |
Collaborator |
A teammate should see but not change it |
Read only |
The whole workspace should be able to view it |
Everyone in the workspace |
A stakeholder without an account needs to view it |
Public link (set an expiry) |
A link has spread too far |
Revoke it from Public Shares |
What’s next?¶
Data governance, the tenant-wide inventory of public links
Data apps, the format most worth sharing live
Members and roles, who can be a collaborator