Page access by collection and document set settings.
Document sets can be tricky to understand. They never override the collection visibility. The following table can help understand the settings options and page visibility with different combinations of access settings.
| Collection state | Document set | Transcriber Access | Notes |
|---|---|---|---|
| Public | (none) | Visible / editable | |
| Private | (none) | Invisible | |
| Read-only | (none) | Visible / not user-editable | |
| Inactive | (any state) | Visible / not owner- or user-editable | The only state that also prevents owners from editing. It's an outlier — every other row in this column is about transcribers, not owners. |
| Public | Private | Visible / editable | Some projects use private document sets to track status, even if the whole collection is editable. |
| Private | Private | Invisible | |
| Read-only | Private | Visible / not user-editable | Only relevant for project-owner navigation; no-op otherwise. |
| Public | Public | Visible / editable | |
| Private | Public | Visible / editable | |
| Read-only | Public | Visible / not user-editable | Not a "correct" combination — this is the only case where a public document set is not user-editable. Owners who want this behavior should set the document set to read-only instead (Read-only collection + Read-only document set). |
| Public | Read-only | Visible / editable | Public collections are always visible and editable. |
| Private | Read-only | Visible / not user-editable | |
| Read-only | Read-only | Visible / not user-editable |
Legend
- Visible / editable — transcribers can see the page and transcribe/edit it.
- Visible / not user-editable — transcribers can cribe or edit it; owners still can.
- Visible / not owner- or user-editable — the page is visible but locked for everyone, including project owners (Inactive collections only).
- Invisible — the page is not shown to transcribe
Read this guide to learn how to enable document sets.