How Confluence Supports Multiple Editors in Real Time Without Conflicts

Confluence allows multiple users to edit the same page or blog post simultaneously through a feature known as collaborative editing. This functionality ensures that team members can work together in real time, seeing each other's changes as they happen, which eliminates the traditional bottleneck of "page locking" or manual merging of different versions.

The core of this experience is built on a specialized service that synchronizes data across all active sessions. Whether you are working on software requirements, meeting notes, or a project retrospective, the collaborative environment allows up to 12 people to contribute to a single document at the same time by default.

Understanding the Mechanics of Collaborative Editing

Collaborative editing in Confluence is not just a visual trick; it is a fundamental shift in how content is stored and processed. In older versions of the software, editing was a solitary task. When a user clicked the edit button, they worked on a personal draft that was invisible to everyone else until the moment they hit "Publish." If two people edited at once, the second person to save would often face a daunting "merge conflict" screen.

Modern Confluence environments have replaced this model with Shared Drafts. Under this system, there is only one version of the "work in progress" for any given page. When the first person enters the editor, a shared draft is created. Every subsequent person who enters the editor joins that same shared draft.

The Role of Synchrony in Real Time Syncing

The seamless experience of seeing a colleague’s cursor move across the screen is powered by a service called Synchrony. Synchrony is a separate process—often running in its own Java Virtual Machine (JVM)—that acts as the synchronization engine for the Confluence editor.

When you type a character, that data is sent to Synchrony, which immediately broadcasts it to all other users currently editing the page. This happens via WebSockets, a protocol that allows for full-duplex communication. If a user’s network environment does not support WebSockets (common in some highly restrictive corporate firewalls), Confluence automatically falls back to XML HTTP Request (XHR), ensuring that the editing experience remains functional, though perhaps slightly less snappy.

Identifying Active Participants

When you are in the editor, Confluence provides visual cues to help you coordinate with your team. At the top of the editing interface, you will see the avatars of everyone currently working on the page. If you need more help, there is a "+" button that allows you to invite specific team members to join the session immediately.

Each editor is assigned a specific color, and their cursor displays their name as they move through the text. This prevents "collision editing," where two people try to change the same sentence at the exact same moment, although the system is robust enough to handle even that scenario without data loss.

What is a Shared Draft in Confluence

The transition to collaborative editing introduced the concept of the shared draft. It is important to distinguish between a "published page" and a "shared draft" to understand how your work is saved.

A shared draft exists from the moment someone starts editing a page and remains active until someone clicks "Publish" or "Update." Unlike the old personal drafts, which were private to the individual creator, a shared draft is accessible to anyone with "Edit" permissions for that space or page.

The Lifecycle of Unpublished Changes

When a page has been edited but not yet published, Confluence marks it with a specific lozenge label: Unpublished Changes. This indicator is visible in the "Recently worked on" list of anyone who has contributed to the draft.

It is crucial to note that these changes are persistent. If you close your browser window without hitting publish, your work is not lost. It remains part of the shared draft. The next person who opens the editor will see exactly what you left behind. This "always-on" saving mechanism removes the anxiety of losing progress due to a computer crash or network interruption.

Comparison Between Shared Drafts and Personal Drafts

To better understand the value of the current system, we can look at the technical differences:

Managing User Limits and Performance

While Confluence is designed for collaboration, there are practical limits to how many people can edit a single page at once before the performance of the editor begins to degrade.

The Default 12 User Limit

By default, Atlassian sets a limit of 12 simultaneous editors per page. This limit is chosen to balance the heavy data load required by Synchrony to keep everyone in sync. If a 13th person attempts to enter the editor, Confluence will display a notification informing them that the editor is full and they must wait for someone else to leave.

Leaving the editor is simple: a user just needs to publish their changes or click "Close." Once the number of active editors drops below the threshold, the "Edit" button becomes available again for others.

Adjusting the Editor Limit for Large Teams

In certain enterprise scenarios, 12 people might not be enough—for example, during a massive "war room" incident response where 20+ engineers are contributing to a single live document. Site administrators have the authority to increase this limit using system properties.

However, increasing this limit should be done with caution. Higher numbers of concurrent editors place a significant strain on the Synchrony service and the end-user’s browser. Each additional editor increases the volume of WebSocket traffic exponentially. If you notice "laggy" typing or cursors jumping around, it is a sign that the limit might be set too high for your current hardware infrastructure.

Administering Collaborative Editing Modes

Administrators have granular control over how collaborative editing functions within their Confluence instance. This is managed via the General Configuration > Collaborative Editing menu.

Turning Collaborative Editing On and Off

There are two primary modes for the editor:

1. On: This is the recommended setting. It enables Synchrony, shared drafts, and real-time collaboration.
2. Off: In this mode, the system reverts to the legacy behavior. Users edit their own personal drafts, and Confluence attempts to merge changes when they save. This mode is typically used only if there are severe technical issues with running Synchrony or if the organization has strict auditing requirements that the current collaborative model cannot satisfy.

Implications of Changing Modes

Switching from "On" to "Off" (or vice versa) is a significant action. If an administrator turns collaborative editing off while team members have active shared drafts, those users will no longer be able to resume editing those specific drafts. They can still view the content in their profile's draft list and copy the text manually, but the seamless editing experience is interrupted.

Before making such a change, it is standard practice to ask all users to publish their work to ensure no "Unpublished Changes" are left in a state of limbo.

Auditing and Version History Limitations

One of the most frequent questions from compliance officers is: "Who exactly made this change?" While collaborative editing is great for speed, it presents some challenges for granular auditing.

Page History and Publishing Attribution

In the current model, Confluence saves a new version in the Page History only when someone clicks "Publish." Because multiple people might have contributed to the shared draft, the entire version is attributed to the person who clicked the publish button.

For example, if Alice, Bob, and Charlie all spend two hours editing a page, but Charlie is the one who finally hits "Publish," the Page History will show that Charlie created the new version. The individual keystrokes and specific sentences added by Alice and Bob are not distinguished in the version history.

The Lack of Versioning in Drafts

Because Confluence is "saving all the time" in the background, it does not create versions of the draft itself. If you make a mistake in the editor and want to revert to what the draft looked like ten minutes ago, you cannot use the standard Page History to do so. You can only roll back to the last published version.

To mitigate this, users are encouraged to publish frequently when making major structural changes, or to manually copy important sections before performing large-scale deletions within a shared draft.

How to Handle Merge Conflicts When Collaborative Editing is Off

In some environments, collaborative editing might be disabled. In these cases, Confluence uses a "Concurrent Editing" system that relies on a merge-on-save logic.

The Conflict Resolution Screen

If you are editing a page and someone else saves a version before you do, Confluence will not automatically update your screen. Instead, when you click "Save," the system compares your version with the newly saved version.

If the changes do not overlap (e.g., you edited the top of the page and your colleague edited the bottom), Confluence will merge them automatically. However, if you both edited the same paragraph, you will be presented with three options:

• Continue Editing: This allows you to look at the conflicting sections and manually integrate your colleague's changes into your work.
• Overwrite: This is the "nuclear option." Your version will replace the other person's version entirely. Their changes will still exist in the Page History, but they will be removed from the current live view.
• Cancel: You discard your changes and accept the version saved by the other user.

This manual process is exactly what collaborative editing was designed to solve, highlighting why the real-time Synchrony engine is so valuable for modern teams.

Troubleshooting Synchrony and Connection Issues

Because collaborative editing relies on a persistent connection between the browser and the Synchrony service, network configuration is the most common source of issues.

Common Symptoms of Synchrony Failure

If Synchrony is not working correctly, users will see an error message stating: "We’re having trouble connecting to the editor." In this state, the editor may become "read-only" or may revert to a limited editing mode.

Common causes include:

1. Port Blocking: Synchrony runs on port 8091 by default. If this port is blocked by a firewall or if another service is using it, the sync engine will fail.
2. Reverse Proxy Configuration: If Confluence is behind a proxy like Nginx or Apache, the proxy must be configured to allow WebSocket headers (Upgrade and Connection). Without these, the real-time updates cannot pass through.
3. SSL Mismatches: If you are using SSL (HTTPS), the connection to Synchrony must also be secure. Issues often arise when there is a mismatch between the SSL certificate on the main Confluence site and the internal Synchrony connection.

How Admins Can Restart Synchrony

Administrators can check the status of the sync engine by going to the Collaborative Editing admin screen. If the status is not "Running," they can attempt to restart it directly from the UI. In Data Center environments, Synchrony can be managed as a standalone cluster, providing higher availability and the ability to scale independently of the main Confluence application.

Best Practices for Successful Real Time Collaboration

To make the most of multiple editors on a single page, teams should follow a few organizational "rules of engagement."

Use Sections and Layouts

When many people are editing at once, it helps to divide the page into sections or use the "Layout" tool. By assigning different people to different columns or rows, you reduce the visual clutter of multiple cursors moving in the same space.

Leverage Comments and Mentions

Instead of deleting someone else's work in real time—which can be jarring—use the inline comment feature or the "@" mention system. This allows for a conversation about the content without disrupting the flow of the shared draft.

Manage Large-Scale Content

If a page becomes too large and frequently reaches the 12-user limit, it is often a sign that the content should be split into child pages. Not only does this improve editor performance, but it also makes the information more digestible for readers.

Summary of Collaborative Editing Capabilities

Collaborative editing in Confluence represents a sophisticated interplay between front-end user experience and back-end synchronization. By using Synchrony and Shared Drafts, Confluence allows teams to move away from the "check-in/check-out" mentality of document management.

• Real-time Interaction: Changes appear instantly for all users.
• Shared Responsibility: One draft serves as the "single source of truth" for the team.
• Automatic Reliability: Changes are saved continuously, protecting against data loss.
• Administrative Flexibility: Limits and modes can be adjusted to suit the organization's technical and compliance needs.

FAQ

Q: Does collaborative editing work on the Confluence mobile app? A: Yes, the mobile experience is designed to work with the same shared draft model, though the interface is optimized for smaller screens.

Q: What happens if an anonymous user edits a page? A: If your space allows anonymous access, anonymous users can join the collaborative session. However, their changes will be attributed to "Anonymous" and they may not see the same warnings when closing the editor as logged-in users do.

Q: Can I see a history of the draft before it is published? A: No. Confluence does not maintain a version history for unpublished drafts. History is only generated upon publication.

Q: Does collaborative editing work with third-party macros? A: Most modern macros are compatible with collaborative editing. However, some older or poorly coded macros may experience display issues when multiple people are interacting with them simultaneously.

Q: Is there a way to turn off collaborative editing for just one specific page? A: No. The setting is global for the entire Confluence instance. You cannot toggle it on a per-page basis, though you can use page restrictions to limit who has the right to enter the editor.

Q: What is the "Synchrony Proxy"? A: It is an internal component that allows Confluence to talk to Synchrony without requiring users to open port 8091 to the outside world. This simplifies configuration for many administrators.

Q: Can I increase the 12-user limit on Confluence Cloud? A: On Confluence Cloud, the limits are managed by Atlassian. While the underlying technology is similar, the specific user caps are determined by your subscription tier and the platform's current performance optimizations.

By understanding these components, teams can effectively utilize Confluence to its full potential, ensuring that collaboration is fast, reliable, and conflict-free.