This article is a comprehensive reference guide for how user attributes are mapped between Google Workspace and CloudM. Understanding these mappings is essential for ensuring data consistency when using Profile Variables in email signatures or automating Organization Details via Inheritance.
How Mapping Drives Automation
CloudM uses these mappings to synchronize data between platforms. This ensures that when you update a field in one location, the change propagates correctly to:
- Signature Templates: Automatically populating email signatures with the correct Profile Variables.
- Smart Teams: Using mapped attributes to trigger dynamic membership rules.
- Inheritance: Mapping shared data (like Office Address) from an OU to an individual's Google Profile.
Full Attribute Mapping Reference
The table below outlines the relationship between CloudM field names, their corresponding Google Workspace attributes, and the variable names used in signature templates.
| CloudM Field Name | Google Workspace Attribute | Profile Variable (Signatures) | Notes |
|---|---|---|---|
| Identity & Account Status | |||
| ID | Primary Email | {{email}} |
Unique identifier in CloudM. |
| Hidden | Include in GAL | - | Controls visibility in the Global Address List. |
| Suspended / Archived | Status | - | Reflects the current Google account state. |
| Personal Information | |||
| First Name | Given Name | {{first_name}} |
- |
| Last Name | Family Name | {{last_name}} |
- |
| Gender / Address Me As | Gender Attributes | {{gender}} |
Mapped from Google's gender schema. |
| Organizational Information (Organization Details) | |||
| Job Title | Organization.jobTitle | {{title}} |
Primary target for Inheritance. |
| Department | Organization.department | {{department}} |
Can be automated via OU-level Inheritance. |
| Company | Organization.name | {{company}} |
- |
| Cost Center | Organization.costCenter | - | Often synced via the CloudManager schema. |
| Manager / Assistant | Relations Attribute | {{manager}} |
Used for reporting line automation. |
| Contact & Location Information | |||
| Telephone (Business) | Phones.work | {{work_phone}} |
- |
| Mobile | Phones.mobile | {{mobile}} |
- |
| Office Address | Addresses.work | {{address}} |
Primary target for Location Inheritance. |
| Building / Floor / Area | Locations Schema | {{building}} |
Mapped to Google's standard location attributes. |
| Custom Attributes (Schemas) | |||
| Extra Information | CloudManager.[custom] | {{extra.[name]}} |
Requires Predefined Extra Information setup. |
Key Considerations
Mappings for core fields like Email and Name are fixed. For organization-specific needs, use Predefined Fields to create controlled lists or Extra Information to sync entirely new data points. Always ensure that any changes are triggered via a directory sync to maintain consistency.