Work continuously, publish deliberately.

Choose the right Knowledge scope

Organization Knowledge

Shared working pages not tied to a delivery project. Open Organization › Knowledge; filter All, Organization, or Projects. Organization-owned pages do not currently expose Publish checkpoint.

Project Knowledge

Pages owned by one project, including the current publication workflow. Open Organization › Projects › Project › Knowledge.

Manage Knowledge

Required to create and administer spaces and templates and to perform other governed Knowledge-management actions.

The organization hub exposes each page's owning scope and working or published state; organization-owned pages are currently working-only, while project pages can carry a published checkpoint. Search and project filters return only pages you are authorized to read. When no pages match, the empty state distinguishes an empty library from an empty search result.

Create a Knowledge space

1. Name the space.Use a durable category such as Handbook, Product decisions, or Runbooks.
2. Confirm the URL slug.Use lowercase letters, numbers, and hyphens. The slug anchors stable page paths beneath the space.
3. Write the rich description.Unsaved creation media remains in a private draft session until the space exists.
4. Create.The new empty root appears in Knowledge spaces.
5. Select a landing page later.After pages exist, edit the space and choose an eligible page as its landing page.

Create and edit a page

1. Enter a title.The creation form needs only a title; Mozaic places the page in the available Knowledge scope and opens its working copy.
2. Edit in Rich mode.Use headings, emphasis, tasks, lists, quote, code block, table, callout, link, footnote, resource reference, media, alignment, size, and tone controls.
3. Use Raw when exact Markdown is useful.Raw input is validated. In a collaborative document, refresh the raw guard if a remote change occurred before replacing the shared content.
4. Preview.Inspect the rendered result without changing the durable document.
5. Watch save state.Saving means the durable operation is still outstanding; Saved means the server acknowledged it. Reconnect if the session drops.

Publish an immutable project checkpoint

1. Finish the working edit.Resolve raw validation and confirm the editor reports Saved.
2. Review Preview.Check structure, links, resource references, callouts, tables, footnotes, and ready media.
3. Choose Publish checkpoint.The button remains unavailable while a durable save is outstanding.
4. Confirm publication.Mozaic records an immutable revision without freezing the working copy.
5. Continue editing if needed.Subsequent working changes do not alter what published readers see until another checkpoint is published.

Use the collaboration panel

The side panel groups related work into four tabs.

History

1. Create a named checkpoint.Capture a meaningful working-copy state without necessarily publishing it.
2. Compare revisions.Select exact revisions and inspect the unified diff.
3. Restore.Restore an earlier revision into a new current working state; history is retained rather than rewritten.

Comments

1. Add a comment.Discuss the page without adding discussion prose to its document body.
2. Edit and inspect history.Comment edits create revisions.
3. Resolve.Close a settled conversation while retaining its record.
4. Moderate when authorized.Hide, restore, or permanently redact abusive or sensitive submitted prose using an audited reason.

Structure

1. Choose the parent and slug.Move the page within its space hierarchy.
2. Save the move.The old path retains a redirect to the stable page identity.
3. Resolve an old link.Use historical-path resolution to confirm where a moved page now lives.

Library

• Save the current working page as a reusable organization- or project-scoped template.
• Upload attachments, wait for malware scanning, and download only clean versions.
• Export the working copy at either scope; project pages also offer Export published after a checkpoint exists.
• Search authorized Knowledge without leaking inaccessible page names or content.

Create templates and manage reusable media

Create a template directly

1. Name the template.Names are limited to 160 characters.
2. Write reusable content.Use the shared rich editor and the media audience appropriate to the owning organization or project.
3. Create.The template appears in the correct owner library.
4. Revise later.Edit name/content and inspect immutable Content history.

Save an existing page

From a page's Library tab, choose to save the working page as a template. The button says Save working page to make clear that unpublished edits, not the last published checkpoint, are the source.

Organization media lifecycle

1. Upload media.Choose an image, audio, video, or file. Success means accepted for safe processing.
2. Wait for Ready.Only ready, authorized assets appear in normal selection.
3. Replace.A replacement creates a new immutable version; old prose continues to reference the exact old version.
4. Retire.Remove an asset from new selection without breaking existing references.
5. Recover in time.Restore a retired asset before its displayed recovery deadline. After the period expires, recovery is unavailable.

Understand what readers receive

Authenticated readers can work with organization or project pages according to their authorization. Anonymous readers receive only an explicitly published project Knowledge checkpoint when the organization, project, and relevant Knowledge resource gates are all public. Scripts and embedded remote content remain inert in rendered Markdown; attachments and media still require their own safe and authorized delivery path.

Common failures and current limits

• Unsaved draft media is private and temporary.
• A published project checkpoint does not freeze ongoing collaboration.
• Existing references stay pinned to immutable media versions.
• Search, page choices, attachments, and exports are authorization-filtered.