EarlyForge
GuidesTeams

Real-time collaboration

Edit articles together live — shared cursors, presence, threaded comments, and version history.

Real-time collaboration

Real-time collaboration lets multiple people edit the same article at once — like a shared document, but built for editorial work. You see each other's cursors, leave comments, and roll back to any earlier version.

Real-time collaboration is available on Pro and above. On lower plans, articles still open in the editor, but only one person edits at a time.

What you get

Live cursors and names

When two or more people open the same article, each person gets a uniquely colored cursor labeled with their name. You can see exactly where teammates are typing and what text they have selected.

Presence avatars

Avatars of everyone currently in the article appear at the top of the editor, and on the article list. This helps your team coordinate and avoid duplicating effort.

Instant, conflict-free sync

Every keystroke and formatting change propagates to all editors within milliseconds — no save-and-refresh cycle. Concurrent edits merge automatically and deterministically, so two people can work in the same paragraph without overwriting each other. Everyone sees the same result.

Threaded comments with @mentions

Leave inline comments on any part of the article and reply to build a thread. Type @ to mention a teammate — they're notified so the right person sees the feedback. Resolve a thread once it's handled to keep the article clean.

Version history

Browse a timeline of saved snapshots and see how the article evolved. Open any earlier version to compare, and restore it with one click if you need to roll back. Nothing is lost — restoring creates a new current version rather than erasing history.

Collaboration covers the full rich-text editor: formatting, images, tables, and citations all sync between editors. AI editor actions you run are reflected live for everyone in the article.

Read-only participants

Not everyone in a session can edit. Viewers and suspended members join in read-only mode — they can open the article and watch live edits as they happen, but they can't type, comment, or change anything. Editing requires at least a Writer role on the article. See Roles and permissions for the full breakdown.

Working in private

Need to draft without an audience? Any member with edit rights can temporarily hide their work-in-progress article from the team using the eye toggle in the editor header. Hidden drafts stay visible to the hider and to organization Owners/Admins (marked with an amber Hidden badge), and become visible to everyone again on publish or when submitted for review. See Private drafts.

A typical workflow

A writer drafts the article

A Writer generates an article from a brief, producing a draft with citations, images, and structure.

They refine with the AI editor

The Writer uses the AI editor to expand thin sections, rephrase sentences, and adjust tone. Changes appear live to anyone else in the article.

An editor joins and reviews

An Editor opens the same article, sees the Writer's cursor, and starts reviewing — checking facts and improving flow. They leave threaded comments with @mentions where they want changes.

Both edit simultaneously

The Writer refines the conclusion while the Editor restructures the introduction. Everything merges seamlessly, and comments keep the conversation in context.

The editor publishes

Once everyone is satisfied, the Editor (who has publishing rights) clicks Publish. The final version captures both people's contributions, and the snapshot stays in version history.

Tips for effective collaboration

  • Split the article — agree on who edits which section to minimize cursor collisions in the same paragraph.
  • Comment instead of overwriting — leave a threaded comment with an @mention rather than silently rewriting a colleague's text.
  • Use version history as a safety net — experiment freely; you can always restore an earlier snapshot.
  • Do a final read-through — even with live editing, review before hitting Publish.

What's next?