When creating or editing CloudM Backup Policies, you may encounter warnings regarding Domain Wide Delegation (DWD) or missing authorization scopes. These permissions are required to ensure CloudM can access and back up your Google Workspace data effectively.
Note: Scope validation options are only visible to Administrators with the relevant permissions.
Common Error Scenarios
Depending on the status of your Domain Wide Delegation, you may experience different behaviors when trying to save a policy:
1. No Domain Wide Delegation Configured
If DWD is not configured at all for your domain:
- You will not be able to save any changes when creating or editing a policy.
- You must configure DWD in the Google Admin Console before proceeding.
- For step-by-step instructions on how to set this up, please see: Provide a Google Cloud service account with domain-wide delegation.
2. Missing Scopes (Partial Configuration)
If DWD is configured but specific scopes required for the selected Item Types (e.g., Chat, Drive) are missing, the behavior depends on the action you are taking:
- Creating a New Policy: You can save the policy, but it will remain disabled (Backup Enabled: Off) until the scopes are fixed.
- Editing an Existing Policy: You will not be able to save any changes until the scopes are updated.
How to Update and Verify Scopes
If your scopes are not up to date, CloudM will provide the necessary information directly in the interface.
- If a warning appears indicating missing scopes, review the list provided.
- Click the Copy button to copy the required scopes to your clipboard.
- Log in to your Google Admin Console.
- Navigate to Security > Access and data control > API controls > Domain-wide delegation.
- Edit the API Client for CloudM and paste the copied scopes into the configuration. Save your changes in Google Admin.
- Return to CloudM and select Verify Scopes.
Sync Delays
Please note that there may be a delay when syncing permission changes from Google to CloudM.
- If you have updated the scopes in Google Admin but CloudM still reports them as missing, please wait a few moments.
- If the issue persists, you may see a message indicating the sync is pending or scopes still need updating. Try verifying again after a short wait.