# Access and sharing

> Choose an audience, assign roles and understand how access is enforced.

Kind: guide · ~3 min · Verified v0.237.0 · Next: [Teams](https://pr-2379-stg.superartifacts.app/docs/teams.md)

## Goal

Give intended people access without relying on forwarded links.

## What you'll have

An audience and named roles for your artifact.

## Needs

Owner access to manage sharing. New artifacts use the workspace default unless visibility is specified; updates preserve their audience. Ask for private explicitly. Editor grants need a paid plan.

```mermaid
flowchart TB
  A["Choose general access"] --> B["Private · Workspace · Public"]
  B --> C["Add named roles"]
  C --> D["Viewer · Commenter · Editor"]
  D --> E["Check project reading too"]
```

## Steps

1. In a published artifact’s **Share** segment, add people by name or email, set each role and review **People with access**. Press **Share** or **Save** to apply changes. Choose general access:

| Audience | Who opens it |
| --- | --- |
| Private | The creator while a member, workspace Owners and named people |
| Anyone at your workspace | Signed-in workspace members; requires a team workspace and entitlement |
| Anyone with the link | Anyone, without sign-in |

2. Name each person's role: **Viewer** opens it, **Commenter** also leaves notes, **Editor** also publishes and restores versions, renames and works with collected data. Editors cannot delete the artifact or manage its audience. Public access alone grants no commenting.
3. Check **Downloads** separately. Turning downloads off restricts platform downloads; it cannot prevent someone copying content they can read.

### Letting Editors edit

Beside **Anyone at your workspace** in **Share**, Owners choose **Viewer** (workspace editing off) or **Editor** (on). Editing is off by default, applies only to workspace Editors and is inactive for Private or Public artifacts. No workspace-wide Commenter setting exists. The dashboard offers the same switch; named Editors keep their explicit grants.

### Sharing by email

Sharing sends an email. In an active Team or Business workspace, inviting a new Commenter or Editor on an artifact can also invite them to the team as a free Commenter. Viewer and artifact-only invitations stay artifact-only. Read the invitation preview: team membership opens everything shared with that team.

### Why enforcement is split

The platform decides access and signs a **grant**, permission for one artifact. The file-serving worker checks it before serving protected content.

### The gate

Without access, readers sign in or request access from the owner. A project can separately lend reading to its audience; the artifact's own address retains its own gate.

### How long access lasts

Narrowing an audience, removing or lowering a named role, or reassigning ownership invalidates older grants on subsequent checks. It cannot recall content already loaded or copied. Membership-only grants last up to 24 hours and do not renew. Explicit sign-out also invalidates older human grants in that browser.

### Taking a copy

Open **Share → Export** or **Export** in the title menu. HTML downloads a ZIP bundle; Markdown a plain `.md` file. For pages without document source, PDF opens your browser’s print dialog. Options depend on your access. The title menu’s **Dashboard** opens that artifact’s dashboard.

## Check it worked

Test as an intended reader and someone outside the audience.

## If not

Check the signed-in email, named role, workspace and project route. Ask an Owner to check invitation policy.

## Variations

Sharing a project may expose private items through it; confirm that audience first.

## Next

[Teams](https://pr-2379-stg.superartifacts.app/docs/teams.md).
