Governance
Knowledge peoplecan actually trust
An owner for every page and a date it must be reviewed by. Verified until a date, never forever. A record of who has read the policy. And, where it matters, nothing published until an approver signs it off.
Reviews · pages you own
3 pagesExpense claims
Owner Rohit K.
Review overdue · 6 daysIncident response runbook
Owner Farhan S.
Due in 4 daysCode of conduct
Owner Ananya R.
Verified · until 3 Dec
[ 01 ] How it works
The life of a trusted page
- 01
Give it an owner
The person who answers for it, and the date it must be reviewed by.
- 02
Verify it
The owner marks it verified until a date; readers see the badge and the date.
- 03
Ask people to read it
A read request goes to people or groups; their confirmations are recorded.
- 04
It comes back for review
When the date passes it enters the review queue and the owner is reminded by email.
[ 02 ] Owners and reviews
Somebody answers for every page
Page owners
A named owner per page, shown to every reader.
Review dates and a queue
Every owner sees what is due and what has lapsed; reminders go by email so an owner who has not opened Knowledge lately still hears.
Verified until a date
Computed when the page is read, never a stored flag, so a lapsed page never wears a green badge.
Pages without owners
Content health lists them, so nothing important is orphaned.
Read acknowledgements
Who has read it, not who was sent it
Ask people or whole groups to confirm they have read a page. The request is tied to the version they were asked about.
Requests by email and in the app
Each person is asked in their notifications and by email, and confirms on the page.
Against the version
If the page is published again, the report shows who confirmed an older version.
A report per page
Who has confirmed, when, and who has not yet.
For the must-reads
Code of conduct, security policy, the new leave rules.
Read requests · Code of conduct
v741 / 48
confirmed
- Meera I.Confirmed today
- Dev P.Confirmed an older version
- Sana M.Not yet · asked by email
Publish approvals
Nothing published until it is approved
For the spaces where a wrong word costs money: a space can require an approver before any page in it is published. On Enterprise.
Submit for review
In an approval space, Publish becomes Submit; the approver is told by email.
Approve or ask for changes
The approver decides; the author is told either way.
Exactly what was submitted
The submission is a snapshot, so approving publishes what was reviewed, not whatever the draft has become since.
People or groups approve
Name the approvers per space; every step goes into the audit log.
Approval · Data retention policy
auditedSubmitted for review
Rohit K. · Mon 10:12
Approved by Priya N.
Legal (group) · Mon 16:40
Published, as submitted
Knowledge · Mon 16:40
[ 03 ] Plans
Which plan has it
| Capability | Standard | Premium | Enterprise |
|---|---|---|---|
| Owners, reviews and verification | Not included | Included | Included |
| Read acknowledgements | Not included | Included | Included |
| Notify everyone | Not included | Included | Included |
| Publish approvals | Not included | Not included | Included |
Full comparison on the pricing page.
[ 04 ] Questions