Skip to main content

Certification and peer review

Certification separates trusted content from drafts. Every card, dashboard and suite sits in one of two buckets: the playpen (the default, where work-in-progress lives) or the certified library. Certifying an item promotes it to the certified bucket and gives it the trust badge everyone sees; uncertifying demotes it back to the playpen.

Who certifies​

Certifying and uncertifying require the Builder tier (T4) or above. Every transition is recorded in the audit log.

One rule is deliberate: certifications are pinned. Once an item is certified it stays certified until someone uncertifies it -- tightening the review policy later never retroactively demotes content your team already trusts.

Peer review​

By default, anyone with certify rights can certify immediately. An Architect (T6+) can require peer review instead, configured per content type (cards, dashboards, suites):

  • Reviewers required -- how many distinct reviewers must approve before the item is certified (0 to 10; 0 means no review needed).
  • Minimum reviewer tier -- the lowest tier an approver may hold (Builder, T4, by default).

Reviewers are designated, not implied​

Review authority is a separate badge, independent of tier. An administrator (T7+) marks individual members as reviewers; holding a high tier -- even Owner -- does not by itself let you approve a review.

The review flow​

  1. A builder (T4+) requests review on the item. A fresh request always starts the approval count at zero.
  2. Designated reviewers approve. The person who requested the review cannot approve it themselves (the four-eyes principle), and each approver must meet the minimum reviewer tier.
  3. When approvals reach the required count, the item is certified and moves to the certified bucket automatically.

While a review is in flight, the item shows its progress -- approvals received out of approvals required.

Scheduled re-review​

A daily evaluator looks for uncertified content that behaves like it should be trusted. Five rules ship by default:

  1. viewed more in the last 30 days than three-quarters of comparable uncertified content;
  2. viewed as much as the median certified item of the same kind;
  3. seen by at least 30 percent of the organisation's members;
  4. first viewed at least 14 days ago (filters out novelty spikes);
  5. not edited in the last 7 days (leaves in-flight authors alone).

An item matched by at least three rules lands in the High-traffic uncertified queue in the Review section of the sidebar, where reviewers can pick it up. Architects (T6+) can toggle individual rules, tune their thresholds, and re-run the evaluation immediately after a change.

What viewers see​

Viewers see the certified badge wherever the item appears, the Certified library in the Workspace section, and per-folder certified counts. The badge is a signal, not a gate -- playpen content remains visible unless it is also marked sensitive.