If user information is missing or appears differently between CloudM and Google Workspace, the issue usually stems from a sync delay, a broken schema link, or unmapped custom fields. This guide helps you diagnose and fix data flow issues.
1. Verifying Data Movement
Before diving into technical settings, verify if the data has actually been triggered to move between platforms.
- CloudM ➔ Google: Changes made in CloudM typically sync instantly. If they aren't appearing in Google, check Directory > Reports > Sync Audit within the Google Workspace Admin Console to see if an API error occurred during the update.
- Google ➔ CloudM: CloudM listens for Google changes via push notifications. If a manual update in Google isn't appearing in CloudM, you should trigger a fresh sync (see Section 5 below).
2. Custom Fields Not Syncing to Google
If you have created Predefined Extra Information (Custom Fields) but the data isn't reaching the Google user profile, the field is likely not "bound" to a schema.
- Navigate to Directory > Profile Fields > Predefined Fields.
- Locate your custom field under the Predefined Extra Information section.
-
Check the Schema column: If this column is blank or set to "None," the field exists only in CloudM.
➔ To fix this, select theCloudManagerschema (or your preferred existing Google schema) and save.
3. Mismatching or "Ghost" Data
Sometimes data appears in the wrong field because of an attribute mapping mismatch.
- Check the Dictionary: Refer to our Mapping Reference to ensure the CloudM field name you are using actually points to the intended Google attribute.
- Admin-Only Fields: Remember that some fields (like Notes or Tags) are CloudM-exclusive and do not write back to Google Workspace by default.
4. Inherited Fields Showing as Blank
If a user profile shows a blank value for a field you know should be inherited (like an Office Address):
- Verify Source Data: Navigate to Directory > Org Units. Edit the target OU and ensure the physical field (e.g., Address) actually contains data. Inheritance cannot "stamp" a blank value.
- Check the "Explicit" Box: In the Inheritance tab, ensure the checkbox for "Explicitly set Profile Property Inheritance" is ticked for that specific OU.
5. Domain Synchronization Settings
If profile data is still not updating as expected, verify the underlying sync engine is healthy.
Check Automatic Sync Status
CloudM should be set to automatically ingest changes from Google. Navigate to:
Settings > Domain Settings > Domain Actions.
- Ensure "Automatic Google Profile Sync" is enabled. If this is disabled, CloudM will only see changes when a manual sync is requested.
Manually Triggering a Sync
If you have corrected a configuration and want to force the changes to propagate immediately, use the Request Sync tool in the same menu:
Settings > Domain Settings > Domain Actions > Domain Synchronisation > Request Sync.