Creator view
Example: three open team questions.
Does the recipient see internal comments?
When you share, you see your document with every comment and note. The recipient sees something else. This concept puts both views side by side, so nothing internal slips out.
What decides it for you?
Does the recipient see internal comments?
The same document. Two views. A concept that shows mistakes before you share.
01 / The basis for deciding
Pick a focus. Each row shows what appears in the example creator view and the recipient view. The mirror view itself is a concept.
4 dimensions · Same standard for both options
Example: three open team questions.
Does the recipient see internal comments?
The public page drops comment anchors, per the register.
Does the recipient see internal comments?
| The criterion | Creator view | Recipient view |
|---|---|---|
| CommentsDoes the recipient see internal comments? | Creator viewAll comments Example: three open team questions. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page | Recipient viewNo comment anchors The public page drops comment anchors, per the register. 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) |
| MentionsWhat happens to @ mentions and references? | Creator viewLinked objects Example: a reference to a project and a task. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page | Recipient viewPlain text only Mentions become text; task and block ids 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) |
| ФайлыDo uploaded images and files come along? | Creator viewVisible Example: an attached brief as a file. Demo exampleFictional sample data. No real companies, no real numbers, nothing is saved or sent. Sample data on this page | Recipient viewNot included Uploaded images, files and non-https links are removed. 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) |
| Mirror viewCan you switch to the recipient view before sharing? | Creator viewNot yet evidenced A switch between the views is 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”) | Recipient viewNot yet evidenced Until then you check the cleaned snapshot after publishing. 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”) |
Source code is evidence of implementation. It does not replace a current live test.
This page shows an idea with sample data. What is real and evidenced is the cleaning of the public page, not the switch.
The mirror view is planned. Cleaning the public page already exists today.
The agency and all content are made up and marked as such.
What a public page leaves out follows a fixed list today.
The mirror view arrives only once it is built and checked.
02 / From feature to moment
Pick a check and do it with a document you are about to share.
Read a document once as if you were the client receiving it.
Find every spot where the team discusses internally.
You know whether the text makes sense without comments.
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 sharing and permissions03 / Before the next step
Publish a snapshot as a read-only page, open the link yourself and check it like a recipient. Revoke it if needed.
Switching is a separate decision. Prepare it and keep the open evidence in view.
Mentions become text, internal parts are dropped, by fixed rules.
Start Peak Docs and share with a role or as a cleaned read-only page. The mirror view follows once it is ready.
Start Peak DocsCleaning of public pages per the Peak Docs register. The mirror view is a concept: planned, not available yet.
Until the mirror view arrives, the checklist on this page helps.
No. The permission mirror is planned and not available yet. The page shows the idea as a labelled concept.
A public page is a released snapshot, sanitized and read-only. Comments and internal content are not part of it.
No, it is a fictitious example that makes the concept tangible.