- \n
- A JumpCloud administrator account<\/li>\n\n\n\n
- JumpCloud Device Package or higher<\/li>\n\n\n\n
- An authorized and active Google Workspace instance<\/li>\n\n\n\n
- A Google user account with the following roles:\n
- \n
- Groups Admin (pre-built role)<\/li>\n\n\n\n
- User management Admin (pre-built role)<\/li>\n\n\n\n
- Custom role with \u2018Domain Management\u2019 admin API privileges<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- You have read through the considerations<\/a> in Get Started: Google Workspace Integration<\/li>\n<\/ul>\n\n\n\n
Attribute Considerations<\/strong><\/p>\n\n\n\n
- \n
- The JumpCloud owned attributes (email<\/kbd>, firstname<\/kbd>, lastname<\/kbd>) are required by Google and bidirectionally sync<\/li>\n\n\n\n
- Optional attributes sync one way:\n
- \n
- Attributes set to Import <\/strong>will not be exported from JumpCloud to Google Workspace <\/li>\n\n\n\n
- Attributes set to Export <\/strong>will not be imported from Google Workspace to JumpCloud<\/li>\n\n\n\n
- Attributes set to Exclude <\/strong>will not be imported or exported<\/li>\n\n\n\n
- Different attributes in the sync can be set to Import<\/strong> or Export<\/strong>, e.g., you can set password <\/kbd>to Export<\/strong> and costCenter to Import <\/strong>in the same sync<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- The default setting for optional attributes, except user state<\/kbd> and password<\/kbd>, is Exclude<\/strong><\/li>\n\n\n\n
- The default setting for the user state<\/kbd> and password<\/kbd> attributes is Export<\/strong><\/li>\n\n\n\n
- The password <\/kbd>and manager <\/kbd>attributes can only be set to Export <\/strong>or Exclude<\/strong><\/li>\n\n\n\n
- Address attributes \u2013 both the JumpCloud and Google Workspace APIs allow multiple addresses for a given type. On export, existing Google Workspace addresses for a given type will be replaced with JumpCloud addresses of that type<\/li>\n<\/ul>\n\n\n\n
Configure User Attributes<\/strong><\/h2>\n\n\n\n
After you’ve authorized the Google Workspace instance<\/a> in JumpCloud, choose the user attributes you want to import, export or exclude. This functionality allows you to centralize the management of these users. <\/p>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/tip-icon.png\")
<\/p><\/div>Tip:<\/strong> \nIf no attributes are selected, i.e., all optional attributes are set to Exclude<\/strong>, only the JumpCloud owned attributes will sync. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Attribute Data Flow<\/strong><\/h3>\n\n\n\n
How does attribute data flow between Google Workspace and JumpCloud after integration<\/strong>? <\/p>\n\n\n\n
- \n
- When you import a user from Google Workspace \u2013 if data exists for a user\u2019s attributes in Google Workspace when they are imported, data is written to the equivalent user attributes in JumpCloud<\/li>\n\n\n\n
- Importation of these attributes must be done before the user exists in JumpCloud<\/li>\n\n\n\n
- When you connect that user to Google Workspace in JumpCloud \u2013 attributes in Google Workspace are automatically overwritten with data from JumpCloud for the attributes set to Export<\/strong>. Further, any subsequent changes made to the user\u2019s attributes in JumpCloud are automatically pushed to the corresponding attributes in Google Workspace<\/li>\n<\/ul>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\")
<\/p><\/div>Note:<\/strong> \nCustom user attributes aren’t supported at this time. You may use the existing attributes for something other than their stated purpose as a short term workaround.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
User Attribute Import<\/strong><\/h4>\n\n\n\n
First name, Last name, and Company email will always be imported from Google Workspace. With the exception of user state<\/kbd> and manager<\/kbd>, you can choose the optional user attributes that you would like to import from Google Workspace for new users and updates. Your chosen attributes will be mapped<\/a> from Google Workspace to the corresponding JumpCloud attribute. <\/p>\n\n\n\n
User Attribute Export<\/strong><\/h4>\n\n\n\n
First name, Last name, and Company email will always be exported to Google Workspace. You can choose the optional user attributes you would like to export to Google Workspace. Your chosen attributes will be mapped<\/a> from JumpCloud to the corresponding Google attribute. If you choose to stop exporting data for an attribute, it is no longer synced with Google Workspace. Subsequent changes made to that attribute in JumpCloud aren’t exported to Google Workspace.<\/p>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\")
<\/p><\/div>Warning:<\/strong> \nTake caution when selecting attributes to export. After you select an attribute to export to Google Workspace, it is immediately overwritten<\/em> with data from JumpCloud for all Google Workspace users managed by JumpCloud, and you could potentially lose data stored for that attribute in Google Workspace. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
User Attributes<\/strong><\/h3>\n\n\n\n
Required attributes<\/strong><\/h4>\n\n\n\n
These attributes are \u201cJumpCloud owned\u201d and always imported from Google Workspace to JumpCloud, and exported from JumpCloud to Google Workspace for bound users:<\/p>\n\n\n\n
- \n
- email<\/li>\n\n\n\n
- firstname <\/li>\n\n\n\n
- lastname<\/li>\n<\/ul>\n\n\n\n
Optional attributes<\/strong><\/h4>\n\n\n\n
Attributes that can only be optionally exported <\/strong>to Google Workspace:<\/p>\n\n\n\n
- \n
- password *<\/li>\n\n\n\n
- manager<\/li>\n<\/ul>\n\n\n\n
Attributes that can optionally be exported <\/strong>to or imported <\/strong>from Google Workspace:<\/p>\n\n\n\n
- \n
- user state *<\/li>\n\n\n\n
- addresses (home)<\/li>\n\n\n\n
- addresses (work)<\/li>\n\n\n\n
- alternate email<\/li>\n\n\n\n
- costCenter<\/li>\n\n\n\n
- department<\/li>\n\n\n\n
- employeeIdentifier<\/li>\n\n\n\n
- employeeType<\/li>\n\n\n\n
- jobTitle<\/li>\n\n\n\n
- phoneNumbers (home)<\/li>\n\n\n\n
- phoneNumbers (mobile)<\/li>\n\n\n\n
- phoneNumbers (work)<\/li>\n\n\n\n
- phoneNumbers (work_fax)<\/li>\n\n\n\n
- phoneNumbers (work_mobile)<\/li>\n<\/ul>\n\n\n\n
(*see Impact of the user state and password settings<\/a> for additional considerations when making selections for these attributes)<\/p>\n\n\n\n
API Attribute Name Table<\/strong><\/h3>\n\n\n\n
The following table outlines how attribute data is exported from JumpCloud\u2019s API and UI to Google Workspace’s API and UI. The attribute listed in the JumpCloud API Attribute Name<\/strong> column is synced to the attribute listed in the Google Workspace API Attribute Name<\/strong> column. The attribute listed in the JumpCloud UI Attribute Name<\/strong> column is synced to the attribute listed in the Google Workspace UI Attribute Name<\/strong> column. See our API documentation<\/a> for more information.<\/p>\n\n\n\n
\n\n
- Attributes set to Export <\/strong>will not be imported from Google Workspace to JumpCloud<\/li>\n\n\n\n
- Optional attributes sync one way:\n
- The JumpCloud owned attributes (email<\/kbd>, firstname<\/kbd>, lastname<\/kbd>) are required by Google and bidirectionally sync<\/li>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\"){kind=icon}
<\/p><\/div>![](\"https:\/\/jumpcloud.com\/wp-content\/uploads\/2023\/10\/Install-yes.jpg\")
<\/td>\n