Start with the outcome you need.
Create your workspace
Verify an account, enroll strong authentication, create or join a private organization, and decide whether you need a project.
Start the setup guide → Organization stewardBring people in safely
Invite members, create teams and versioned roles, scope assignments, review audit evidence, and control publication.
Configure access → ContributorPush an existing repository
Create a private repository, issue a least-privilege HTTPS credential, connect Git, and protect the exact target branch.
Set up source control → Open-source maintainerPublish and accept contributions
Publish each intended scope, verify the anonymous view, accept work reports, and review proposals from private contributor forks.
Open a project carefully →An organization is the workspace. A project is optional.
Mozaic never creates a hidden personal workspace. Your account can belong to one or more organizations. An organization owns its membership and collaboration context; create a project only when work needs a shared delivery boundary for source, reviews, pipelines, packages, project work, or project knowledge.
Your identity and security
A verified email, strong password, passkey or authenticator, recovery codes, and your organization switcher live at account scope.
People and collaboration
Home, Inbox, News, Chat, Calendar, Knowledge, People, Teams, Time, governance, media, and billing belong here.
A delivery context
Work, project Calendar and Knowledge, repositories, reviews, pipelines, packages, and webhooks share one named project.
An exact object
Repositories, pull-request snapshots, runs, package versions, work items, pages, and events keep stable identities and history.
Publishing an organization, project, feed, or other resource never silently publishes its descendants. Anonymous access requires every necessary ancestor and the resource itself to be deliberately public.
Coordinate without creating a project first.
Find what needs attention
Use personal Home lanes, requested reviews, delivery signals, notifications, authorized search, News publishing, and private or channel conversations.
Open the communication guide → Project WorkMove an item through delivery
Create a board and workflow, file work, assign people, add typed fields and relationships, resolve it, and retain the transition history.
Plan and track work → Organization and project working copiesBuild durable knowledge
Edit with collaborators, wait for durable acknowledgement, compare history, preserve redirects, and publish an immutable checkpoint from project Knowledge when a stable reader view is needed.
Build knowledge → Calendar · TimePlan a meeting and reconcile time
Create scoped events with privacy controls, respond to invitations, run a timer, complete the week, and understand edit and readiness policy.
Coordinate schedules →Follow exact code from branch to package.
Create, import, browse, and govern source
Use blank repositories or verified .bundle imports, show-once credentials, browser editing, comparisons, exact-ref branch policies, archive, and export.
Review the code that was actually proposed
Open a pinned snapshot, request reviewers, leave draft line feedback, synchronize new commits, satisfy merge policy, and merge atomically.
Review a pull request → Immutable execution planRun the checked-in pipeline
Write valid .mozaic/pipeline.yml, dispatch an exact revision, inspect jobs, logs, TRX and artifacts, and handle trust or indeterminate results.
Create a feed and publish a version
Issue a bounded token, configure a standard client, restore and push, map explicit upstreams, inspect provenance, and manage immutable package lifecycle.
Use package feeds → Outgoing webhooksDeliver selected project events
Choose a safe HTTPS endpoint and finite event set, store the signing secret, verify signatures, inspect failures, and redeliver intentionally.
Configure webhooks → Plan and service creditsUnderstand capacity before a run
Read the active quota and usage snapshot, submit a manual prepaid reference, and trace reservations and the append-only credit ledger.
Review billing and limits →Routes appear when your effective claims allow them.
Mozaic combines a role version with its assignment scope. An organization assignment covers descendants; a project or exact-resource assignment is narrower. Guides name the relevant claim when a workflow is restricted. An Owner, Maintainer, Contributor, Auditor, or Billing manager label is useful orientation, but it is not a substitute for checking the effective scoped claim.
| Workflow | Typical required claim | Scope that matters |
|---|---|---|
| Invite people and change membership | manage_members and manage_roles | Organization |
| Create teams and manage membership | manage_teams | Organization |
| Create or govern repositories | manage_source | Organization, project, or resource |
| Review code | review_code | Organization, project, or resource |
| Run pipelines | run_pipelines | Organization, project, or resource |
| Manage feeds and lifecycle | manage_packages | Organization, project, or resource |
| View payment details | manage_billing | Organization |
If a link described in a guide is absent, first check the active organization/project and then ask an access steward to review your effective assignment. An unavailable or unauthorized object may intentionally look like a missing route.
What these guides cover today.
The documentation describes the operated hosted public beta as implemented. It covers member and customer administration inside an organization, not operation of the Mozaic platform.
| Area | Current behavior |
|---|---|
| Version control | Git smart HTTP and Git LFS. SSH Git and URL-based repository import are not current; imports use a verified Git bundle. |
| Delivery | Declarative, isolated pipelines with a .NET-focused sample path and NuGet v3 package feeds. General deployment environments and OCI registry hosting are not current. |
| Collaboration | News, direct/group/channel Chat, Inbox, search, Work, Knowledge, calendars, time capture, teams, and media are current. |
| Meetings | One-off calendar coordination with validated external meeting links. Mozaic does not create provider meetings or host native audio/video. |
| Workforce configuration | Time projects/types, edit policy, and break-policy versions are current. Schedule-profile and member-profile assignment screens are read-only. |
| Repository publication | Anonymous repository reading exists for already published resources, but the current repository Access screen is informational and does not change publication. |
The service is pre-release and does not yet publish a stable support window. Export repositories and other durable records as appropriate for your project.
How to use this documentation.
- Navigation path
- Labels such as Project → Code → Repository → Settings → Branch rules refer to visible product navigation, not a fixed hostname.
- Working copy
- Editable state that members can continue changing. Knowledge and other rich content can preserve this separately from public state.
- Published checkpoint
- An immutable revision deliberately selected for public readers. Publishing is never inferred from an editable draft.
- Fresh authentication
- A recent passkey, security-key, or authenticator confirmation required before a sensitive change. Use the offered Refresh MFA path, then return to the form.
- Show-once value
- A credential, recovery set, invitation link, or webhook secret that cannot be read again. Copy it before leaving the successful creation screen.
- Conflict
- Another actor or process changed a versioned resource. Reload it, review the current state, and deliberately apply the change again.