This article explains how to manage custom user attributes within CloudM. Use Predefined Extra Information to ensure custom data (like Employee IDs, Cost Centers, or Onboarding Dates) is synchronized and consistently mapped between CloudM and Google Workspace.
Understanding Schemas and Custom Attributes
Google Workspace uses schemas as physical containers for custom attributes.
- Default Attributes: Standard fields provided by Google like Given Name or Email.
-
Custom Schemas: Organization-specific containers (e.g.,
CloudManager) that hold your unique data points like EmployeeID.
Navigation: Directory > Profile Fields (Select your top-level OU).
Note: Custom attributes are managed at the domain level to ensure organization-wide consistency.
Method A: Defining Custom Fields in CloudM (CloudM > Google)
When you define a new field in Predefined Extra Information, CloudM uses the Google Directory API to create a physical schema in Google Workspace called CloudManager.
- CloudM Field Name: The label used within the CloudM interface.
- Type: The data format (Text, Boolean, Number). Note: This cannot be changed once saved.
-
Schema: By selecting
CloudManager, you instruct CloudM to manage the physical creation and two-way sync of this attribute in Google.
Method B: Syncing Existing Attributes (Google > CloudM)
If you already have custom data stored in Google Workspace schemas, you can map it to CloudM.
- Define the Schema in Google: Ensure your schema exists in the Google Admin Console (See Google's Guide).
-
Connect to CloudM: In the
Predefined Extra Informationtab, select your existing Google schema and specific fields. CloudM will then "listen" for data changes from these attributes.
Mapping Reference
The mapping process ensures the CloudM Field Name (the label you see) points to the correct Google Workspace Schema (where the data lives).
| CloudM Field Name | Typical Schema Mapping |
|---|---|
| Area | CloudManager.area |
| Building | CloudManager.building |
| Department | CloudManager.department |
| Cost Center | CloudManager.costCenter |
Technical Considerations & Sync Triggers
- Type Locking: Data types (Text vs Number) are locked upon creation to prevent database corruption.
- Sync Direction: Changes made in CloudM sync instantly to Google Workspace. Changes made in Google sync back to CloudM within minutes via Push Notifications.
-
The Inheritance Trigger: To push new schema values to users via Inheritance, you must trigger a directory sync:
Settings > Domain Settings > Domain Actions > Domain Synchronisation > Request Sync.