// Explanation
How approval works
ArtifactBridge separates work an agent wants to do from work your team has approved. That is what lets several AI tools share one trustworthy starting point.
Reads the current workspace, creates work, asks questions and proposes changes.
Reviews the change and decides whether it becomes the next shared version.
Imported sources and managed documents are different
An imported Google Doc, Notion page or OneDrive file keeps an external source. ArtifactBridge reads and synchronizes that source. A managed ArtifactBridge document can evolve through versioned changes and review.
Why this matters across AI tools
If one person uses Claude Code and another uses Codex, memory inside either tool is not enough. ArtifactBridge gives both tools the same shared documents, decisions and reviewed versions.
Memory helps one AI remember. ArtifactBridge helps a team decide what everyone’s AI should treat as approved.
Governed and working documents
A governed document requires human review before an agent’s proposed change becomes the current version. Use it for shared policies, approved plans, customer-facing material, and other content where a reviewer must decide.
A working document can allow direct agent updates. Use it for agent notes, draft progress, or other material where direct updates are intended. Review rules can still require approval; the effective document and folder settings decide.
Configure direct changes
- Open Document settings.
- Inspect Can agents make direct changes?
- When the control is off, agent changes require review. When on, the document is a working document.
- The document owner must resolve active proposals before changing this setting.
Folder settings set the corresponding behavior for new documents and can contribute an inherited review requirement. Check the individual document before treating it as directly editable.
Three separate controls
| Control | Question it answers |
|---|---|
| Audience | Is this material intended for people, agents, or both? |
| Sharing and access | Who is allowed to read it? |
| Review behavior | Must a human approve agent changes? |
Changing the audience does not make a document private. Allowing direct agent changes does not make it public. See Sharing and access.
Approval applies to a specific action
Starting an agent, accepting a document proposal, approving an import, and allowing an external comment are different decisions. Read the requested action, target, and content each time. Permission to read a source does not authorize every write to it.
Keep evidence with the result
Ask agents to cite source documents and record relevant versions. Accepted document changes create history; Room messages preserve the discussion. The audit log records supported workspace events for authorized owners and admins. These records help explain what happened, but you must still verify the content before approval.