Doxbrix is a multiplayer editor. Several people can work on the same page at the same time, see each other's cursors, and propose changes — without ever overwrit...
Doxbrix is a multiplayer editor. Several people can work on the same page at the same time, see each other's cursors, and propose changes — without ever overwrit...
Doxbrix is a multiplayer editor. Several people can work on the same page at the same time, see each other's cursors, and propose changes — without ever overwriting each other's work.
Real-time presence
When more than one person has a page open, you see everyone who's there:
- Avatars of all active collaborators appear in the top bar.
- Live cursors show where each person is working, updated in real time.
- Presence refreshes continuously while a page is open, so the list reflects who's actually there right now.
Changes merge automatically as everyone types — there are no save conflicts and no "someone else edited this" errors. The editor converges concurrent edits to a consistent result under the hood.
Viewing vs. editing
Presence distinguishes between people who are actively changing the page and people who are just watching:
- Editing — someone is actively making changes.
- Viewing — someone has the page open but isn't editing (or is on a page they can't edit, such as one that's in review or published).
This makes it easy to run a live walkthrough — a teammate can watch your edits stream in without the risk of accidentally changing something. Pages that are In review or Published open read-only, so collaborators there are always viewing, not editing.
Proposing changes
There are two complementary ways for someone to propose a change rather than make it silently:
| Use a [comment](/collaborate/comments) when… | Use the [review workflow](/collaborate/review-workflow) when… |
|---|---|
| You want to suggest a specific wording change or flag an issue on a block. | A whole page's changes are ready for sign-off before publishing. |
| The author should decide and apply the edit. | A reviewer should **Approve** or **Request changes** for the page. |
A subject-matter expert with Viewer access can comment precise corrections on any block — without edit-and-publish rights — and the doc owner stays in control of what ships. Reviewers can also edit a page directly during review for small fixes (a typo, a broken link) rather than bouncing it back for a one-character change.
A typical collaboration flow
Co-authors open the page and write in parallel — cursors and avatars show who's where.
Reviewers and SMEs leave comments on specific blocks, @-mentioning whoever needs to weigh in.
The author addresses each comment, resolves the threads, and clicks Submit for review.
A reviewer approves (or requests changes), and the page publishes per your governance policy.