Peak Docs · Security & privacy
Who sees what.
Plainly handled.
Security and privacy in Peak Docs, explained plainly: roles per document, private notes and read-only links you release yourself. No security promises.
Which change do you want to check?
Per document you share on purpose: edit, comment or view. The same check also applies to real-time co-editing.
Clear roles,
clear limits.
- 01Roles
- 02Private
- 03Sharing
A real story starts with its release.
What was hard before?
Files sit in shared folders and nobody knows exactly who can see what. In Peak Docs one rule decides access: the owner, an explicit share as edit, comment or view, and the role in the workspace.
This pattern shows the structure. It doesn't tell a real customer case yet.
The path to change
Access in three layers.
The roles
Per document you share on purpose: edit, comment or view. The same check also applies to real-time co-editing.
One role per person and documentEvidence format · not filled in yetThe starting point.
In the original.Original excerptInsert the released passage here.
A / ObservationWhich concrete friction is visible in this source?Example · a document's shares The private part
Notes are private by default, and your continuous notes page belongs to you alone. Images and files in a document are as visible as the document itself.
Private stays privateEvidence format · not filled in yetOne step.
Traceable.BeforeOriginal processSource evidence requiredChangeConcrete interventionProduct view and date requiredExample · private note Sharing outside
For readers without an account you, as the owner, release a read-only version by link. Guest access and password-protected links are planned.
Only the version you releaseEvidence format · not filled in yetThe result.
With a yardstick.- Observation
- Not evidenced yet
- Period
- Open
- Source & release
- Pending
Without released data this statement stays open.
Example · read-only link
What can be evidenced
What you can set today.
The evidence is still pending
No certifications, audits or security figures on this page. Peak Docs makes no claims here that are not proven.
The sculpture does not depict a customer.
One perspective.
With name and release.
Beyond the single case
What understandable permissions do.
One rule instead of many exceptions
Who may see a document is decided by the same rule everywhere: in the library, in search and in co-editing.
Key ideaPredictable access
Honest about limits
An audit trail exists in part. Guest access, password links and approval workflows are planned and not available today.
Key ideaA clear status instead of promises
What this article is based on.
Sample overview with made-up data, not a customer story and not a security promise. Roles per document, private notes and read-only links exist in Peak Docs; the audit trail is partly built, guest access and password links are planned.
- Editorial demo
Editorial example with made-up sample data. Co-editing, library and search, comments, versions, references to customers, projects and tasks, health signals and link sharing exist in Peak Docs today; everything else is marked as preview, concept or planned.
- Evidence pending
No released Peak Docs customer story. No customers, quotes or results are shown.
Share exactly what you want to share.
Create your first document and share it on purpose to view, comment or edit.
Frequently asked questions
Which roles exist per document?
Besides the owner there are shares to edit, comment and view, plus the role in the workspace.
Can I share documents outside?
Yes, as a read-only version by link that you release as the owner. Guest access and password links are planned.
Does Peak Docs have security certifications?
This page names no certifications. It only describes the permissions that are built today.