Skip to main content

Google Workspace Pre-Guide

info

**In a Google Workspace environment, customers do not create Google Cloud projects or service accounts.**You only need to approve domain-wide delegation once for the service account provided by SHIELD DRM and provide one admin account for integration.

Document Scope​

This document is**Google Workspace(Google Drive)**This is the environmental criteria. The prerequisites for the Microsoft 365 (SharePoint · OneDrive · Teams) environment are "Preliminary GuidePlease refer to 」.

Customer Preparation #1 · #2 is independent of the cloud services being used.CommonIt applies from #3 and is for Google Workspace environment only.

Preparation at a Glance​

OrderPreparation ItemsExecution Locationperforming entity
#1Security365 Portal Membership Registration and SettingsSecurity365 PortalClient Company Administrator (Common)
#2Firewall AllowanceCustomer FirewallClient Company (Common)
#3Google Workspace User SynchronizationSHIELD IDSHIELD ID Manager
#4Preparing Google Admin PrivilegesGoogle Admin Consolesuper administrator
#5Domain-Wide Delegation (DWD) ApprovalGoogle Admin ConsoleSuper Administrator
#6Check shared drive settingsGoogle Admin Console · Google DriveGoogle Admin

#5의 승인은 Google에 반영되기까지up to 24 hoursThis may take time. Please consider this time when scheduling the implementation.

After completing the preparations, the integration procedure conducted on the SHIELD DRM management page is 「Google Workspace Integration Setup Guideis located in.

Preparation #1 | Security365 Portal Membership Registration and Setup​

The registration and setup process is the same regardless of the cloud service. The "Pre-Guide" of사전 준비 #1Follow.

It is recommended to create the administrator account for Google Workspace customers as a Google Workspace administrator account.

Preparation in Advance #2 | Firewall Allowance​

The allowed URLs are common regardless of the cloud service. The "Pre-Guide" of사전 준비 #2Apply the table as is. There is no SHIELD DRM URL to add specifically for Google Workspace.

  • **Google Workspace service URL is allowed by the customer company itself.**must be provided. It is communication for users to use Google Drive and is not exclusive to SHIELD DRM items.
  • Google Drive's change notifications and Google Drive API calls areBetween Google and SHIELD DRM ServiceIt will be conducted. There is no need to open the firewall in the direction coming into the client company's network.

Preparation in Advance #3 | Google Workspace User Synchronization (SHIELD ID)​

SHIELD DRM is my driveUser UnitIt is processed as such. Therefore, each user account of the SHIELD ID must be linked to a Google Workspace account. This corresponds to the procedure for synchronizing Microsoft users in a Microsoft 365 environment.

  • Connection is**SHIELD ID Personnel Integration (Google Workspace Inbound Provisioning)**It is created with. The setup method is in the SHIELD ID document 「Google Workspace Inbound Provisioning Settings - Customer UsePlease refer to 」.
  • **It is recommended to set up automatic synchronization.**If there is no automatic synchronization, the account will not be linked even if it exists in both SHIELD ID and Google Workspace, and the SHIELD ID administrator must perform a manual synchronization.
  • Unconnected users cannot install channels in My Drive. In the admin page, there is지원하지 않음is displayed as.
info

Shared drives are independent of user account connections. This preparation is to protect my drive.

Preparation in Advance #4 | Google Admin Privileges​

Google Workspace integration requires two administrator accounts with different roles. In the Microsoft 365 environment,Global AdministratorPermissions corresponding to Google Workspace'sSuper Administratoris.

PurposeRequired PermissionsUsage Point
Domain Delegation Approval (사전 준비 #5)super administratorIntroduction once
Integration Administrator AccountDrive and DocsAdministrator privilegesContinuing during service operation

Integration Administrator Account​

SHIELD DRM uses the permissions of this account to query the list of shared drives and to add or remove service accounts as members of the shared drives. It does not need to be a super admin account.

  1. Google Admin Console(admin.google.com) → account → Administrator Role → Create a new roleSelect.
  2. Enter the role name. (e.g:SHIELDRM)
  3. in permissionsservice → Drive and DocumentSelect and save.
  4. Assign the created role to the administrator account for integration use.
  5. the account's**Send the email address to the SHIELD DRM operations manager.**is done. Currently, the operations manager registers.
  • Integration account hasLicense to use Google Drivemust be assigned, and the Drive service must be in the organizational unit of that account.SettingsIt must be in a state.
  • Integration account isEmail domain same as users synchronized with SHIELD IDIt must be.
  • Predefined roles instead of custom rolesServices AdminYou can assign __PH_0__. However, since it includes the configuration permissions of services outside of Drive, custom roles are recommended.

Unlike the Microsoft 365 environmentMIP label creation, publication, and tenant name verification are not required.

Preparation in Advance #5 | Domain-Wide Delegation (DWD) Approval​

To access the organization's Google Drive, the SHIELD DRM service account must be in the Google Admin Console.Domain-Wide DelegationYou must approve it once. This is the procedure corresponding to app permission consent in the Microsoft 365 environment.

The values required for approval are two.

itemvalue
Client IDThe SHIELD DRM Operations Manager conveys.
OAuth Scopehttps://www.googleapis.com/auth/drive

Approval Process (Administrator, 1 time)​

  1. Google Admin Console(admin.google.com) Log in with the administrator account.
  2. Security → Access and Data Management → API ManagementMove to.
  3. Domain Delegation ManagementClick.
  4. Newly addedClick and enter the client ID and OAuth scope from the table above.
  5. ApprovalClick.
  6. Check if the client ID and scope are displayed as is in the list.Even if there is a typo in the range, registration will succeed, but integration will fail.

Notes After Approval​

  • Until the approval is reflectedup to 24 hoursThis may take some time. Access may fail even if the settings were completed before reflection. Do not repeat the approval in this interval.
  • If you delete the client ID from the approval list,Integration across the entire organization has been suspendedIt will happen. It affects all drives, not just a specific drive.

Preparation in Advance #6 | Check Shared Drive Settings​

Shared drives are used by multiple users, so SHIELD DRM does not act on behalf of a specific user.Processing under the name of the service accountdoes. When you install a channel on the shared drive, SHIELD DRM operates with the permissions of the administrator account for integration.service account 참여자 Automatically Added by RoleIt is done. The client company does not need to add the service account directly.

warning

**The service account is displayed in the shared drive member list. Even if it appears to be an unfamiliar account, do not delete or lower its role.**If there is no service account or if it does not have write permissions, document processing will fail on that drive. A service account does not consume a Google Workspace license.

  • The service account is an account outside the customer's domain. In the shared drive settings,If access by external users is not allowedUnable to add service accounts, channel installation fails. Please check the external sharing settings of the protected shared drive in advance.
  • My drive does not require this preparation. My drive is handled under the owner's own authority.

Differences to Know Before Getting Started​

The Google Workspace environment is not the same as the Microsoft 365 environment in terms of functionality. Do not assume feature equivalence when considering adoption.

  • Policy enforcement in the cloud isDocument DecryptionThere is one thing. Automatic encryption at the time of upload and MIP label conversion are not provided.
  • Re-protection of documents downloaded to PC**Document Security(Endpoint)**is in charge of.
  • Google Chat attachments are not included in the scope of support.
  • A newly created shared drive and a new user's My Drive do not have channels automatically installed.

Detailed actions and constraints are 「Guide to Using Google WorkspacePlease refer to 」.

Reference Document​