Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
As of September 18, 2026, WordPress does not include real-time collaboration in WordPress 7.0. The closest route for editing the same post or page together is an experimental feature in the Gutenberg plugin, enabled under Settings → Writing. It is not a stable, built-in production feature: test it with your site’s content and plugins before relying on it. For lower-risk teamwork, use individual WordPress accounts and choose a workflow suited to the task—live editing, inline feedback, or a separate shared document.
What “real-time collaboration” means in WordPress
Real-time collaboration means more than letting several people access a site or take turns editing. In a live shared editor, collaborators can work in the same document at the same time, see some indication of one another’s activity, and have changes synchronized without manually passing a file back and forth.
That is different from editorial review. A comment or suggestion workflow lets a writer and editor exchange feedback, but it does not necessarily let both people edit the same post simultaneously. A shared document created inside WordPress is another distinct workflow: it may support joint work without being a normal published post or page.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThese distinctions matter because the current WordPress options do not all solve the same problem. The Gutenberg experiment is aimed at collaborative editing in the post editor. Multicollab’s WordPress.org listing describes inline editorial comments and feedback. The Docs plugin describes shared documents within wp-admin. Neither of the latter listings, by itself, establishes a supported way to co-edit an existing post or page live.
#1 Best Overall
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Current WordPress status
WordPress Core said on September 18, 2026 that real-time collaboration had been removed from WordPress 7.0. The effort had been tested in Gutenberg, but it was not included in that WordPress release. A June 2026 Core outreach post describes an ongoing test effort ahead of WordPress 7.1; it is not a commitment that the feature will ship in 7.1.
The current test route is to activate the Gutenberg plugin and enable the collaboration setting under Settings → Writing. That is a Gutenberg-plugin experiment, not a setting available to every standard WordPress installation. Core contributors have said the design should move toward a server-aware approach controlled by WordPress Core. As contributor Chris Zarate put it, “Collaboration should be server-aware, with WordPress Core in control.”
Gutenberg 22.6 release notes describe the project’s implementation at that point: a Writing settings toggle, presence indicators, visible cursors and block selections, and synchronization for the post title, content, and excerpt. The notes also mention work on disconnections, revision restores, and performance metrics. Those details describe that Gutenberg project release, not a guarantee that every site, version, host, or post type behaves the same way.
Rank #2
- Used Book in Good Condition
Choose the workflow that matches the work
| Option | Where people work | What it supports | Important qualification |
|---|---|---|---|
| Gutenberg real-time collaboration experiment | The post or page editor | Live collaborative editing; Gutenberg 22.6 notes describe presence, cursors, block selections, and synchronization of title, content, and excerpt. | Experimental, not included in WordPress 7.0. Enable through the Gutenberg plugin’s Settings → Writing controls; test compatibility and recovery on your own site. |
| Multicollab | Block editor review workflow | Its WordPress.org listing describes inline comments, tagging, replies, and editorial feedback. | The free version is no longer maintained, and version 4.4 (April 4, 2024) removed real-time co-editing and guest collaboration. Later Gutenberg compatibility is not established by the vendor page reviewed here. |
| Docs plugin | A shared document in wp-admin | The listing describes documents with link-based, email-invited, existing-user, or restricted access; it says collaborative editing requires Gutenberg or WordPress 7.0. | The listing states WordPress 6.9 or higher and tested through 6.9.8. Because the Core team says collaboration was removed from WordPress 7.0, verify the stated prerequisite and behavior before choosing it. |
| External document editor | A document outside the WordPress post editor | Can be used for drafting or review before content is transferred into WordPress. | Collaboration behavior depends on the service and document type. Google’s cited help page, for example, only establishes a limitation for client-side encrypted files: real-time collaboration is unavailable for those files. |
Use the Gutenberg experiment only if people need to edit the same WordPress post or page at once and the team is prepared to test an experimental feature. Choose an editorial-feedback tool when the main need is to leave comments and discuss changes. Choose a shared-document workflow when collaborators need a document in WordPress but are not necessarily editing a published post. An external editor can work for drafting, but it adds a transfer or publishing step.
How to enable and test the Gutenberg experiment
The steps below describe the route documented by WordPress Core for the Gutenberg plugin. Menu labels and behavior can vary with the installed plugin and site configuration. Do not treat a visible toggle as proof that the feature is production-ready.
- Use a staging site first. Create a non-production copy or test environment with the same relevant WordPress version, theme, plugins, and content setup as the live site. Avoid using a live, time-sensitive article as the first test.
- Give each tester an individual account. Add the people who will test through your site’s user-management controls and assign only the role or capabilities they need. Do not share one username and password; the WordPress.com user guide specifically advises inviting people with their own credentials and choosing a role.
- Install and activate the Gutenberg plugin. The collaboration route described by Core requires the plugin. Check that the installed plugin version exposes the relevant setting; the feature is not part of WordPress 7.0 core.
- Open Settings → Writing. Find and enable the Real Time Collaboration option if it is present. The June 3, 2026 Core outreach post identifies this as the enablement path for recent Gutenberg versions.
- Open one test post or page in two separate sessions. Sign in as the separate test users, open the same item, and make small, distinguishable edits. Observe whether presence indicators, cursors, selections, title, content, and excerpt changes behave as expected for your installed Gutenberg version.
- Test recovery and interruptions before inviting a full team. Disconnect one session, reconnect, restore a revision, and check whether the final saved content is correct. The Gutenberg 22.6 notes mention reliability work related to disconnections and revision restores; testing these cases on your own setup is still necessary.
- Check the content types and plugins you actually use. Repeat the test on the post types, blocks, editorial plugins, and publishing workflow the team depends on. If a plugin or automated process modifies content, verify that those writes do not overwrite or conflict with collaborators’ edits.
- Decide whether the result is safe for your workflow. Document which versions and content types passed, which users can edit, and what recovery procedure the team should follow. If a test exposes lost, duplicated, or confusing edits, disable the experiment and use a non-live workflow until the issue is understood.
Accounts, roles, and permission boundaries
Every collaborator should use a separate account. Shared credentials make it harder to identify who made a change, complicate access removal when someone leaves, and give each person the same access whether or not their work requires it. Invite users through the site’s user controls and select the role or capabilities appropriate to the assignment rather than granting broad administrative access by default.
The exact permissions depend on the site’s role configuration, custom capabilities, post type, and plugins. Confirm that each person can edit the intended content and that people who only need to review cannot unintentionally publish or alter unrelated material. A collaboration indicator or shared-document link does not replace WordPress permissions; confirm the access model separately for each tool.
Recommended Free Tools
WordPress.com’s user guide recommends adding a team member as a site user with their own credentials and an assigned role, and warns against giving someone your username and password. On a self-hosted site, available roles and invitation controls can differ based on the installation and configuration, so verify the permissions in that specific site.
What can go wrong with the experiment
The design concern described by the WordPress Core team is that the current experiment merges edits in browsers while the server may later receive a save or another automated write without understanding what collaborators changed. In that situation, one edit could overwrite another, and overlapping edits could merge in a confusing way. These are documented architectural risks, not a claim that every collaboration session loses work.
- One person’s change disappears: Compare the current content with revisions, identify the last known good version, and restore or reapply changes carefully. Do not assume that the most recent browser view is the authoritative saved version.
- Overlapping edits look wrong: Pause edits, have one editor coordinate the repair, and compare the affected blocks with each collaborator’s intended changes. Avoid having several people repeatedly overwrite the same section while troubleshooting.
- A user cannot edit: Check that they are signed into the correct account and have the required permissions for that specific item and post type. An account that can view a document may not have permission to edit or publish a post.
- The setting is missing: Confirm that the Gutenberg plugin is active and that the installed version includes the experiment controls. The setting is not a standard WordPress 7.0 core control.
- A plugin or automated process changes content: Test its interaction in staging. A server-side write that runs outside the shared browser session may not account for what collaborators have changed in that session.
- A disconnect interrupts work: Reconnect and verify the saved content before continuing. Use the revision history as a recovery aid, but test the restore process rather than assuming it resolves every conflict.
Core’s stated direction is to make collaboration server-aware and keep WordPress Core in control. That is a design direction, not confirmation that a replacement architecture has shipped. Until a production-ready core feature is announced, treat the Gutenberg implementation as an experiment whose suitability must be established on your own stack.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to assess the available plugins
Multicollab: feedback rather than current live co-editing
The WordPress.org listing for Multicollab focuses on in-editor inline comments, mentions or tagging, replies, and editorial feedback. Its free version is identified as no longer maintained. The changelog says version 4.4, dated April 4, 2024, eliminated real-time co-editing and guest collaboration; older changelog references to simultaneous work should not be read as evidence that the current free version offers it.
The vendor’s compatibility page lists Gutenberg 14.2–21.9, WordPress 6.4 and above, and PHP 8.0 and above, and says the plugin is not compatible with Classic Editor. The Gutenberg range ends before the 22.6 release notes cited above, so compatibility with later Gutenberg versions is not established on that page. Review the current listing and vendor documentation before using it, especially if the task requires live co-editing rather than review comments.
Docs: a separate shared-document workflow
The Docs listing describes creating documents inside WordPress and sharing them through a link, email invitation, existing-user access, or restricted access. That is a different object and workflow from editing an existing post or page. The listing says it requires WordPress 6.9 or higher and is tested through 6.9.8; it also says real-time collaboration requires Gutenberg or WordPress 7.0. Since Core says collaboration was removed from WordPress 7.0, do not infer that this stated prerequisite guarantees live editing on a current WordPress installation. Verify the plugin’s current behavior and requirements before adopting it.
Compatibility and rollout checklist
Before using collaborative editing for real publishing work, evaluate the complete environment rather than checking only whether the feature switch appears.
- WordPress and Gutenberg versions: Record both versions and confirm the experiment is actually available in that combination.
- Content coverage: Test the exact post types, blocks, title, excerpt, and custom editing components your team uses.
- Concurrent activity: Test two or more accounts editing distinct areas, then overlapping blocks, so the team knows how conflicts appear.
- Interruptions and recovery: Simulate a disconnect, reload, revision restore, and return to the document after another user has saved.
- Automated or plugin writes: Include any plugin, scheduled process, or workflow that updates post content or metadata.
- Permissions: Check the actions allowed for each collaborator and remove access when it is no longer needed.
- Fallback: Decide how the team will pause live editing and return to sequential editing or comments if synchronization behaves unexpectedly.
The Core posts and release notes document the experiment’s status and the concerns behind its redesign; they do not establish tested compatibility for every hosting environment or plugin combination. Your staging results are the relevant evidence for your own site.
Quick Recap
Sources and further reading
- Make WordPress Core: Moving to a server-aware approach for collaboration (September 18, 2026).
- Make WordPress Core: Announcing a collaborative editing outreach effort for 7.1 (June 3, 2026).
- Make WordPress Core: What’s new in Gutenberg 22.6? (February 25, 2026).
- WordPress.org Plugin Directory: Multicollab.
- Multicollab Help Center: Compatibility + Limitations (last updated December 16, 2025).
- WordPress.org Plugin Directory: Docs.
- Google Docs Editors Help: Collaborate on encrypted files in Docs, Sheets & Slides.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
