- \n
- A JumpCloud administrator account<\/li>\n\n\n\n
- JumpCloud SSO Package or higher or SSO \u00e0 la carte option<\/li>\n\n\n\n
- A JumpCloud API key<\/a> to connect Bob and JumpCloud<\/li>\n\n\n\n
- A Bob administrator account<\/li>\n\n\n\n
- If you will be configuring SSO, request your company ID from HiBob support<\/a><\/li>\n\n\n\n
- Review the latest JumpCloud Integration<\/a> article in the HiBob Help Center. <\/li>\n<\/ul>\n\n\n\n
Important Considerations<\/strong><\/p>\n\n\n\n
- \n
- If an employee is not assigned to any SSO provider they will be able to log in to Bob using only their Bob username and password<\/li>\n\n\n\n
- Each employee can be assigned to only one SSO provider<\/li>\n\n\n\n
- If all employees are required to log in using SSO, you will not be able to set up any additional SSO integrations with Bob<\/li>\n\n\n\n
- If you select people by condition and an employee who is currently assigned to another SSO is included in the conditions they will not be able to log in to Bob<\/li>\n\n\n\n
- We recommend creating a separate JumpCloud administrator account to generate the JumpCloud API key for this integration<\/li>\n\n\n\n
- To use the Staged<\/strong> user state in JumpCloud, contact the HiBob\u2019s support team<\/a> and ask them to change the default behavior. By default, the Bob integration will only create the user in an Active <\/strong>or Suspended <\/strong>(inactive) user state unless they change this default behavior\n
- \n
- We recommend setting your user state default to Staged<\/strong> to make it easier to identify users who have been imported and to complete the onboarding process without granting access. You can learn more about the Staged user state at Manage User States<\/a><\/li>\n<\/ul>\n<\/li>\n\n\n\n
- To automatically send the JumpCloud activation email when the integration changes the user state of a user from Staged<\/strong> to Active<\/strong> in JumpCloud, contact your Bob implementation manager to submit an engineering request or contact the HiBob Support Team<\/a> to create support ticket to enable this functionality.<\/li>\n\n\n\n
- We recommend that you do not set a default password in Bob. Setting a default password prevents you from being able to send an Activation email allowing the user to set their own password. You can set one later in JumpCloud if needed<\/li>\n\n\n\n
- Bob users created before the JumpCloud integration was configured will be synchronized in JumpCloud once one of the mapped properties is updated for those users in Bob<\/li>\n\n\n\n
- Bob users not in JumpCloud will be created<\/li>\n\n\n\n
- Bob users who have already been created in JumpCloud will be updated <\/li>\n\n\n\n
- You can request HiBob’s support team<\/a> to trigger an all employees’ synchronization to JumpCloud<\/li>\n\n\n\n
- The Bob integration is managed and supported by the HiBob team. Please contact the HiBob support team<\/a> first if you encounter issues with the integration<\/li>\n<\/ul>\n\n\n\n
Configuring the Identity Management Integration<\/strong><\/h2>\n\n\n\n
To get your JumpCloud API Key<\/strong><\/h3>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\")
<\/p><\/div>Note:<\/strong> The Admin API key needs to belong to an Admin that has one of the following roles; Manager, Administrator or Admin with Billing. Creating an administrator service account with one of these roles is one way to ensure the integration isn’t dependent on a specific admin account.<\/p><\/div><\/div><\/div>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\")
<\/p><\/div>Warning:<\/strong> \nOnce a new API key is generated, this revokes access to the current API key. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal<\/a> with the administrator account you want to use to generate the API key for this integration.<\/li>\n\n\n\n
- Click your initials in the top right corner.<\/li>\n\n\n\n
- Select My API Key<\/strong>.<\/li>\n\n\n\n
- Click on Generate New API Key<\/strong>.<\/li>\n\n\n\n
- Copy the API Key and store it securely, or leave this tab open while you complete the integration configuration steps in the SP.<\/li>\n<\/ol>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\")
<\/p><\/div>Important:<\/strong> \nThis is the only time your API key will be visible to you. Store it somewhere safe, such as the JumpCloud Password Manager<\/a>, so you can access it later.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
To configure the JumpCloud default user state<\/strong><\/h3>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/tip-icon.png\")
<\/p><\/div>Tip:<\/strong> \nReview <\/a>Manage User States<\/a> for more information.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Navigate to Users > Settings<\/strong>.<\/li>\n\n\n\n
- Set Manual \/ Single User API<\/strong> and CSV Import \/ Bulk User API<\/strong> Import values to the default user state you prefer for users created by the integration<\/li>\n\n\n\n
- Click Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n
To configure the JumpCloud integration in Bob<\/strong><\/h3>\n\n\n\n
<\/p><\/div>Tip:<\/strong> \nThe Identity Management Integration is solely configured in Bob. Review Bob’s JumpCloud integration<\/a> for more information.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Login to Bob<\/a> with an administrator account.<\/li>\n\n\n\n
- From the left bottom menu, navigate to Settings > Integrations<\/strong>.<\/li>\n\n\n\n
- Under Provisioning<\/strong>, select MANAGE <\/strong>in the JumpCloud<\/strong> tile.<\/li>\n\n\n\n
- Click + Add connection<\/strong>.<\/li>\n<\/ol>\n\n\n\n
<\/p><\/div>Note:<\/strong> \nYou can add multiple connections.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Enter a name for your connection and your JumpCloud API key<\/strong>.<\/li>\n\n\n\n
- Click Connect.<\/strong><\/li>\n\n\n\n
- In the Provision settings<\/strong> section, click Edit<\/strong> (pencil).<\/li>\n\n\n\n
- When to provision<\/strong> – select when you want users created in JumpCloud: \n
- \n
- On profile creation in Bob<\/li>\n\n\n\n
- On start date<\/li>\n\n\n\n
- Before start date (specify number of days)<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
![\"\"](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2023\/06\/Bob-provisioning-by-date-1024x380.png\")
<\/figure><\/div>\n\n\n- \n
- Who to provision<\/strong> – select the users to be synced to JumpCloud: \n
- \n
- All Employees <\/li>\n\n\n\n
- Select by condition – users meeting a certain condition, or a chosen set of users <\/li>\n\n\n\n
- Select by name – the list can be further filtered to users whose work email address matches a specified domain(s)<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
![\"\"](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2023\/06\/Bob-who-to-provision-1024x349.png\")
<\/figure><\/div>\n\n\n- \n
- Default user settings<\/strong> – select the value for What status do users in Jumpcloud start with?<\/strong> This controls in which user state a user is created. The choices are:\n
- \n
- Inactive until start date<\/strong> – creates users in the suspended<\/strong> user start and the automatically changes the user state to active<\/strong> them on their start date. Resources cannot be assigned to users when they are in a suspended user state in JumpCloud<\/li>\n\n\n\n
- Active<\/strong> – creates users in the active<\/strong> user state. User have access to all assigned resource when they are in an active user state<\/li>\n\n\n\n
- Inactive<\/strong> – creates users in the suspended<\/strong> user state<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n
<\/p><\/div>Note:<\/strong> \nIf you want user created in the Staged <\/strong>user state, which is recommended, you must contact Bob support<\/a> and have that option enabled.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
- \n
- Deactivation<\/strong>:\n
- \n
- Enabled<\/strong> – users are automatically suspended in JumpCloud when they are made inactive or deleted in Bob. (recommended)<\/li>\n\n\n\n
- Disabled<\/strong> – the user state remains unchanged in JumpCloud when they are made inactive or deleted in Bob<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- User credentials<\/strong>:\n
- \n
- Enabled<\/strong> – all users are created with the specified default password in JumpCloud<\/li>\n\n\n\n
- Disabled<\/strong> – a user is created without a password in JumpCloud. (recommended)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Scroll back to the top of the Provisioning settings and click Save.<\/strong><\/li>\n\n\n\n
- Data mapping<\/strong> – select your desired attributes to be sent from Bob into JumpCloud and click Save<\/strong> when finished. You can also create custom attributes to map to JumpCloud by clicking on the + Add field<\/strong> button at the bottom of the section. <\/li>\n<\/ol>\n\n\n\n
<\/p><\/div>Tip:<\/strong> \nRefer to Bob’s Map data for integration provisioning<\/a> article for more information.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
\nBob User Attributes<\/h3>\n
\n - Disabled<\/strong> – a user is created without a password in JumpCloud. (recommended)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Disabled<\/strong> – the user state remains unchanged in JumpCloud when they are made inactive or deleted in Bob<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Enabled<\/strong> – users are automatically suspended in JumpCloud when they are made inactive or deleted in Bob. (recommended)<\/li>\n\n\n\n
- Active<\/strong> – creates users in the active<\/strong> user state. User have access to all assigned resource when they are in an active user state<\/li>\n\n\n\n
- Inactive until start date<\/strong> – creates users in the suspended<\/strong> user start and the automatically changes the user state to active<\/strong> them on their start date. Resources cannot be assigned to users when they are in a suspended user state in JumpCloud<\/li>\n\n\n\n
- Default user settings<\/strong> – select the value for What status do users in Jumpcloud start with?<\/strong> This controls in which user state a user is created. The choices are:\n
- Who to provision<\/strong> – select the users to be synced to JumpCloud: \n
- Click Connect.<\/strong><\/li>\n\n\n\n
- From the left bottom menu, navigate to Settings > Integrations<\/strong>.<\/li>\n\n\n\n
- Navigate to Users > Settings<\/strong>.<\/li>\n\n\n\n
- To automatically send the JumpCloud activation email when the integration changes the user state of a user from Staged<\/strong> to Active<\/strong> in JumpCloud, contact your Bob implementation manager to submit an engineering request or contact the HiBob Support Team<\/a> to create support ticket to enable this functionality.<\/li>\n\n\n\n
- We recommend setting your user state default to Staged<\/strong> to make it easier to identify users who have been imported and to complete the onboarding process without granting access. You can learn more about the Staged user state at Manage User States<\/a><\/li>\n<\/ul>\n<\/li>\n\n\n\n