Reference

Governance: review, publish, and agent permissions

How review and publishing work in Memrio, and what each agent permission — read drafts, can edit, can publish — actually allows.

Updated 2026-09-19View as markdown

The point of the registry is that agents read what a person approved. Three mechanisms make that true: versions with review, per-agent page sets, and explicit agent permissions.

Versions and review#

Editing a published page never changes what agents see until a new version is approved. A submitted version carries a change summary and shows up for reviewers, who approve or reject with a note. Workspaces can require review for everyone or let editors publish directly.

Each page has a review frequency. When it lapses the page is flagged so someone re-confirms it is still right — stale knowledge is the failure mode this exists to prevent.

Page sets#

An agent sees only pages in its set. Add individual pages or whole subtrees. A support bot gets customer-facing policy; an engineering agent gets runbooks; neither sees the other. Sections group pages but are not readable themselves.

Agent permissions#

SettingDefaultEffect
ActiveonPaused agents reject every MCP call with 403.
Read draftsoffFor test agents only. Lets the agent read draft and in-review pages.
Can edit pagesoffAdds get_page_source, create_page, update_page, append_to_page. Writes are submitted for review.
Can publish without reviewoffTrusted bots only. Writes go live immediately for every other agent.

Human roles#

RoleCan
ViewerRead pages and activity.
EditorCreate and edit pages, submit for review.
AdminApprove versions, manage agents and keys, change workspace settings.
OwnerEverything, plus billing and members.

Audit trail#

Activity records every human and agent action — created, edited, submitted, approved, rejected, published, key created, key revoked. The request log records every MCP call with the pages hit. Together they answer “why did the agent say that?” with a page and a version number.