Skip to main content
This section outlines the access and permission requirements for your organization’s Google Workspace administrators, internal users, and external collaborators. Understanding these requirements ensures your organization is properly licensed and configured before beginning the Client-side Encryption (CSE) integration with CryptoHub.

​
Administrator requirements

To set up Google Workspace CSE for your organization, you must be a Super Admin for Google Workspace.

​
User requirements

Users must conform to the following requirements:
  • Users need a Google Workspace Enterprise Plus, Google Workspace for Education Plus, or Enterprise Essentials license to use CSE to:
    • Create or upload files
    • Host meetings
  • Users can have any Google Workspace or Cloud Identity license to:
    • To view, edit, or download an existing file encrypted with CSE
    • Join a CSE meeting
  • To view or edit encrypted files, users must use either Google Chrome or Microsoft Edge.
  • To join a CSE meeting, users must be invited or added during the meeting. Knocking isn’t available for CSE meetings.
  • Access to CSE files and meetings depends on your organization’s CSE policies.
Users with a consumer Google Account (such as Gmail users) can’t access CSE files or participate in CSE meetings.

​
External user requirements

External users must conform to the following requirements:
  • During the beta, external users must have a Google Workspace license to access your content encrypted with CSE. Users with a consumer Google Account or a
visitor account can’t access files encrypted with CSE.
  • External organizations must also set up CSE, either in the Admin console or with a .well-known file.
  • Your external encryption service must allowlist the third-party IdP service used by the external domain or the individuals you want to use CSE. You can usually find the IdP service in their publicly available .well-known file.