Latest in AI
Encrypted Google Docs Can Now Support Live Editing: How to Test the Beta
Check beta eligibility, separate sharing roles from key access, and find out why an encrypted Google Doc still says Wait to edit.
Two people open the same encrypted Google Doc. One starts typing and the other sees “Wait to edit.” That was the normal workflow for client-side encrypted Docs before Google announced its real-time collaboration beta on November 20.
If your team gets access, I would test two files, not one: a new encrypted Doc created after enrollment and a pre-beta encrypted Doc. That comparison tells you more than opening an old document and concluding that the rollout did not work.
Check whether your domain is enrolled
Google's beta announcement lists Enterprise Plus, Education Standard, Education Plus, Frontline Plus, Assured Controls and Assured Controls Plus as eligible.
An admin requests access through the registration form linked in the announcement and chooses a test or production domain. Google sends onboarding and testing instructions after the domain is allowlisted. Real-time editing is enabled by default for newly created client-side encrypted Docs in enrolled domains. Holding an eligible subscription is not the same as being enrolled.
This announcement covers Google Docs. It does not establish real-time editing for encrypted Sheets or Slides, or promise to upgrade older encrypted Docs in place.
Test a new encrypted Doc with three people
Start from a work or school account with client-side encryption enabled and identity verified. In Docs, go to File > New > New encrypted document, then select Create. Google's encrypted-file setup guide shows the creation path and what to check if the option is missing.
Use dummy text. Give two colleagues Editor access and a third Commenter access, assuming each is authorised to open the encrypted file. Have both editors type in separate paragraphs at the same time, then check whether each sees the other's changes without waiting or refreshing. Ask the commenter to leave a note and confirm they cannot edit the body.
Repeat with the same people in a pre-beta encrypted Doc that is safe to test. Google's standard encrypted-file collaboration guide describes the one-editor-at-a-time experience. If the new file works live and the old one still shows “Wait to edit,” do not assume the old file is broken.
Check the sharing role and key access separately
A sharing invitation and access to decrypt a document answer different questions. If someone cannot open the file, first confirm that they are signed into the invited account and that the relevant identity and key access are in place. If they can open it but only comment, check their sharing role before touching the encryption setup.
Google says an authorised collaborator with key access can work in a shared beta-enabled Doc even if their own domain is not enrolled. That is not a way around your external-sharing policy. Include an outside collaborator in the pilot only if you already have an approved reason to share with them.
Do not change key services to fix a pilot
The Workspace admin guide says key-service migration is not supported for real-time encrypted Docs during the beta. Switching the key service for an organisational unit or group, or moving a beta document between units with different key services, can make affected files read-only. Google advises keeping the old service active as a backup to preserve read access during a planned migration.
For an initial test, leave the key setup alone. Before moving a real workflow, also check what that template depends on. Google's setup guide warns that features such as linked charts can become static when adding encryption to a copy, and Apps Script and add-ons can be removed. Live typing does not restore those features.
I'm Paras. I work at the intersection of AI, engineering and distribution, and I help technical teams turn product releases and setup details into guides people can actually use. Book a 30-minute call.