Share and control access

Make artifacts public, private, email-allowlisted, or accessible through scoped share links.

Artifacts supports quick public sharing and stricter controls for private work. Every change runs through the same authorization layer and is recorded in audit history.

Read current access

CLI

artifacts artifact access get --artifact-id ARTIFACT_ID

Set who can see it

Access is controlled by two switches plus an optional email allowlist. The CLI takes the whole access object as JSON:

Public

Anyone with the URL can view it.

artifacts artifact access set \
  --artifact-id ARTIFACT_ID \
  --json '{"publicView":true,"publicEdit":false,"viewerEmails":[]}'

Private

Only owners, workspace members, allowlisted emails, authorized keys, or share links can view it.

artifacts artifact access set \
  --artifact-id ARTIFACT_ID \
  --json '{"publicView":false,"publicEdit":false,"viewerEmails":[]}'

Private artifacts require a plan with private artifact entitlements.

Email allowlist

Named people sign in with a verified, matching email.

artifacts artifact access set \
  --artifact-id ARTIFACT_ID \
  --json '{"publicView":false,"publicEdit":false,"viewerEmails":["[e-mail]"]}'

Share links

Share links grant one role for a single artifact, and can expire. Use editor only when the recipient should be able to update the artifact.

Create

artifacts share create \
  --artifact-id ARTIFACT_ID \
  --role viewer \
  --expires-at 2026-06-30T12:00:00.000Z

The matching REST routes:

POST /api/artifacts/:artifactId/share-links
GET  /api/artifacts/:artifactId/share-links
POST /api/share-links/:shareLinkId/revoke

Revoking stops future access through that link while keeping audit records intact.

Review audit events

Artifact

artifacts audit list --artifact-id ARTIFACT_ID --limit 50

Audit retention depends on your plan:

Plan	Retention
Free	7 days
Pro	90 days
Team	365 days

Patterns that work well

• Public view for artifacts you’ll paste into issues, pull requests, or docs.
• Private + email allowlist for specific teammates.
• Expiring viewer share links for ad hoc review.
• Editor share links sparingly — revoke them once the collaboration window closes.
• Narrowly scoped API keys for automation.