Skip to main content

Audit what Cognizon knows

Updated Nov 4, 2026

The Knowledge page is where an admin reviews everything Cognizon has learned for the workspace: what's pending approval, what's currently active, and the full history of changes. Use it to approve or correct shared memory before the whole team relies on it.

Review and manage shared knowledge

  1. Open Knowledge from the sidebar. This page is visible only to workspace admins.
  2. On Review suggestions, check the statement, source, and audience for each pending item, then click Approve, Edit then approve, or Reject.
  3. On Shared knowledge, browse everything currently active for a dataset, group, or the workspace; an admin can also add an entry by hand with New entry when needed.
  4. On Change history, see every past change, with filters; open an entry's history to Restore an earlier version or Retire the current one.
  5. Still on Review suggestions, use Scan for shared facts to find facts that several people have independently told Cognizon and turn them into candidates — this only proposes them, it never approves anything automatically.

Good to know

  • The Knowledge page itself is visible only to workspace admins.
  • Approving or rejecting a pending item is available on every plan; adding entries by hand and the full change history need the Team plan or higher.
  • Dataset-level suggestions can also be approved from My Data by whoever can edit that dataset.
  • Retiring an entry keeps its version history and audit trail; it only stops it being used as active context.

FAQ

Who can open the Knowledge page?

Only workspace admins.

What happens when I approve a suggestion?

It becomes active shared context for the audience it was proposed for — a dataset, a group, or the whole workspace.

Can I edit a suggestion before approving it?

Yes. Click Edit then approve on the pending item to change it before it goes live.

What's the difference between the tabs?

Review suggestions is the pending inbox, Shared knowledge is what's currently active, Change history is every past change, and Assistant is a copilot for working with knowledge.

Does retiring an entry delete it?

No. Retiring stops an entry from being used as active context, but its version history and audit trail stay — you can restore an earlier version later.