01 / Evidence fileRole: view, comment or edit
Workspace share
Who sees itMembers with a role
Owner, an explicit share (edit, comment, view) or a workspace role.
Who gets access to the document?
Peak Docs · Sharing and permissionsRegister checked · Guests and password links planned
Don't just share.Release on purpose.
A document travels further than it should. Here you compare the two ways Peak Docs knows today: a share with a role in your workspace and a public read-only page via link.
What decides it for you?
Who gets access to the document?
Access on purpose
Who may do what, and why?
Two ways to share. The same questions. Clear roles instead of guesswork.
01 / Your first perspectiveWorkspace shareRole: view, comment or edit
02 / Your second perspectivePublic read-only pageReleased snapshot via link
01 / The basis for deciding
Two ways. The same questions.
Pick a focus. Each row asks both ways the same question. Anything planned is marked as planned.
4 dimensions · Same standard for both options
02 / Evidence fileReleased snapshot via link
Public read-only page
Who sees itAnyone with the link
A read-only page the owner deliberately publishes.
Who gets access to the document?
| The criterion | Workspace share | Public read-only page |
|---|---|---|
| Who sees itWho gets access to the document? | Workspace shareMembers with a role Owner, an explicit share (edit, comment, view) or a workspace role. Backed by codeFeatures marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register) | Public read-only pageAnyone with the link A read-only page the owner deliberately publishes. Backed by codeFeatures marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register) |
| What comes alongWhich content reaches the other side? | Workspace shareThe living document Comments, history and references depending on the role. Backed by codeFeatures marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register) | Public read-only pageA cleaned snapshot Mentions become text; internal ids, comment anchors and uploaded files are dropped. Backed by codeFeatures marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register) |
| Taking it backHow do you end access again? | Workspace shareRemove the share When the role changes, access changes, in live rooms too. Backed by codeFeatures marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register) | Public read-only pageRefresh, expiry, revoke The link can be refreshed, given an expiry or revoked. Backed by codeFeatures marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register) |
| External peopleCan clients or partners work along? | Workspace shareNot yet evidenced Guest access and password-protected links are planned, not available yet. Evidence pendingPlanned – not available yet. Shown on this page as a concept only. Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (status “open”) | Public read-only pageRead only External people read the released snapshot; they don't comment. Backed by codeFeatures marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace. Source checked: Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register) |
Transparency is part of the comparison.
Source code is evidence of implementation. It does not replace a current live test.
Our standard
No hidden rights.Roles with a clear limit.
Access is checked in the database, not only in the interface. What doesn't work today is marked as planned here, not promised.
Roles you understand
View, comment, edit.
Each role says what it allows. What is missing is marked as planned.
- 01
One check everywhere
The same role check applies in the document and in the live collaboration room.
- 02
Publishing is deliberate
Only the owner releases a public page, with a cleaned snapshot.
- 03
Planned stays planned
Guests, password links and admin policies are still open.
02 / From feature to moment
Test it with a real document.
Pick a check and run it with a document from your work, on paper or in your workspace.
Where do you want to start?
Take a real document and ask who should read, comment on or change it.
Your checkFor both options
The same task
The role list
Write down who should view, comment on and edit one document.
What you check
Every person has exactly one role with a reason.
Backed by code
Features marked “built” or “partial” in the Peak Docs requirement register. A register doesn't replace your own test in your workspace.
Source checked:
Peak-Admin/peak-one@5f93511 · docs/prd/peak-docs-prd.md (requirement register)Task selected. No test run.
See the steps03 / Before the next step
From the role list to the share.
In Peak Docs you share with the share button in the document. Shares and notices reach the people involved in their Inbox.
- 01Set roles per document
- 02Release the public snapshot deliberately
- 03Plan expiry and revocation
Switching is a separate decision. Prepare it and keep the open evidence in view.
From plan to share
Role first. Then the link.
Sharing is a decision, not a reflex.
The next sensible step
Share without giving up control.
Start Peak Docs and release your first document on purpose, with a role or as a read-only page.
Start Peak DocsRoles, shares and public read-only pages per the Peak Docs register. Guest access, password links and admin policies are planned.
Stay in control
You release. You revoke.
A public page can be refreshed, given an expiry or revoked.
Frequently asked questions
Which roles exist?
Owner, editor, commenter and viewer, plus your workspace roles. Permissions apply the same everywhere, including live editing.
How do I share a document outside?
You release a read-only version as a public page. You can refresh it, give it an expiry date or revoke it.
Are there guest access or password links?
Not yet. Guest access and password-protected links are planned and not available yet.