The News, Explained
On November 20, Google announced a beta for writing, editing and commenting together in Google Docs protected by client-side encryption. Google says these encrypted documents previously required one person to edit at a time. The initial beta covers Docs; simultaneous editing in Sheets and Slides is described as a later addition. Source Source
Client-side encryption, or CSE, encrypts a file in the user’s browser before cloud storage. An organization controls access to encryption keys through an external key service. Editing a document together and granting the keys needed to read it serve different roles. This announcement expands collaboration while retaining that key control. Source Source
An administrator of an eligible organization must apply with test or production domain information and have the domain added to the beta allowlist. Real-time collaboration then applies by default to newly created encrypted Docs in that domain. Authorized users with key access can also edit existing real-time collaboration Docs shared with them even if their own domain is outside the beta. The announcement’s availability list includes Enterprise Plus, Education Standard and Plus, Frontline Plus, Assured Controls and Assured Controls Plus. Source
Retrieving file content has an initial beta limitation. Vault, used for organizational retention and search, and the Takeout data-export feature do not yet support bulk content export for these real-time collaboration files. The application says policies such as legal holds are respected, and Vault’s interface shows the file name and Document ID. A bulk export that includes a real-time collaboration file produces a specific error code in its metadata, or information about the file. Source
The documented alternative for obtaining content is manual. An end user can download and decrypt a file, or an administrator can use existing tools to transfer ownership to an authorized account for manual download and decryption. Decryption uses a key to make encrypted content readable again. Finding a file name or Document ID and obtaining its contents therefore involve different steps in the application. Source
Changing key services or internal management units also has conditions. KACLS is the external key service controlling access to encryption keys stored outside Workspace. The application says the beta does not support KACLS migration or maintain editability when files move between organizational units, or OUs, within an organization. It separately describes two-key mitigations for continuity of access during migration and interface warnings about possible loss. Full KACLS migration support is presented as a plan for general availability. Source Source
The application also warns that data may be impossible to restore if customer-managed keys are lost or deleted. Third-party key management and identity services remain subject to their providers’ terms and availability conditions. Google says it collects metrics such as the number of real-time collaboration files and users, and latency, to provide, test and improve the beta, while not analyzing file content. Source
Existing Alpha organizations must also register under the beta terms to create new real-time collaboration Docs. Organizations that do not register retain access to their existing files. The application gives no guarantee of a general release and says final functionality may differ. Bulk export and Sheets and Slides support are later plans to distinguish from the functions currently available. Source
OYOPICK’s Take
Moving from editing an encrypted document one person at a time to working together is welcome. For an organization judging this beta, we would consider work that requires retrieving content alongside the co-editing experience. Finding an item by Document ID and obtaining document contents in bulk require different preparation. Identifying who can download and decrypt files, and which authorized account would do that work, should make the current scope easier to understand.
If bulk export and key-service migration support arrive, we hope easier editing is matched by continuity in moving and managing data. Until then, defining which documents will use the beta and how their content will be retrieved seems useful for an adoption decision. Clear timing and scope for Google’s follow-up features would help organizations distinguish procedures they can use today from capabilities still to come.