- \n
- If you are using a SCIM integration to create users in JumpCloud from external identity sources, such as the BambooHR and Okta integrations, the value for the Settings<\/strong> > User Management<\/strong> > Default User State for User Creation<\/strong> > Manual\/Single User API<\/strong> setting is what will determine the default state for these users.<\/li>\n\n\n\n
- For users created in the Active<\/strong> user state, user emails are still determined by the method used to create a user in JumpCloud and the password status. See the Building Users section in Get Started: Admin Implementation<\/a> to learn more. <\/li>\n\n\n\n
- If you are using the AD integration:\n
- \n
- Staged users are not provisioned to AD.<\/li>\n\n\n\n
- The UserTakeoverAction<\/strong> value should be changed to retain<\/kbd>. Otherwise, the password status will change back to a pending status when the user is associated with AD from JumpCloud. To learn more about this setting and the difference between setting the value to retain and deactivate, see Advanced Configurations for AD Sync<\/a> to learn more. <\/li>\n\n\n\n
- The default value you set for Settings<\/strong> > User Management<\/strong> > Default User State for User Creation<\/strong> > Manual\/Single User API<\/strong> is what will determine the default state for users imported from AD.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
To configure the Default User State:<\/strong><\/p>\n\n\n\n
- \n
- Log in to the JumpCloud Admin Portal<\/a>.<\/li>\n\n\n\n
- Go to Users > Settings<\/strong>.<\/li>\n\n\n\n
- Select a default user state for each method outlined under Default User State for User Creation<\/strong>.<\/li>\n\n\n\n
- Click Save.<\/strong><\/li>\n<\/ol>\n\n\n\n
![\"\"](\"https:\/\/jumpcloud.com\/wp-content\/uploads\/2023\/05\/Snag_170cb992.png\")
<\/figure>\n\n\n\n![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/tip-icon.png\")
<\/p><\/div>Tip:<\/strong> \nThe default user state for users created from the AD integration or one of the SCIM integrations (e.g., Okta, BambooHR) will be determined by the value specified for the Manual \/ Single User API \/ ADI \/ SCIM API<\/strong> setting.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\")
<\/p><\/div>Note:<\/strong> \nA new user can be created from the Admin Portal (select USER MANAGEMENT <\/strong>> Users <\/strong>> ( + )<\/strong> or from an application Identity Management integration (USER AUTHENTICATION <\/strong>> SSO <\/strong>> select an application <\/strong>> Identity Management <\/strong>> manual import<\/strong>.) You can learn more about the listed user creation methods in these support articles:<\/p>\n\n\n\n
- \n
- Import Users into JumpCloud from CSV Using the PowerShell Module<\/a><\/li>\n\n\n\n
- Single user creation through the API<\/a><\/li>\n\n\n\n
- Bulk users creation through the API<\/a><\/li>\n<\/ul>\n <\/div><\/div><\/div><\/div>\n\n\n\n
Understanding User States<\/strong><\/h2>\n\n\n\n
A user state indicates where a user currently is in the identity lifecycle. User states allow you to control access to JumpCloud provided resources. Set the default user state from Settings<\/strong> > User Management<\/strong> > Default User State for User Creation<\/strong>.
The following user states are available:<\/p>\n\n\n\n- \n
- Staged <\/strong>– Easily identify users who still need to be onboarded. Preassign all the resources and policies new users will need on their start dates without granting access. The user account will not be provisioned in most cases until the user state is changed to Active. You can activate, suspend, or delete a user from this user state. Staged users are billed as normal users.<\/li>\n\n\n\n
- Active <\/strong>– Immediately provision a user account and enable a user\u2019s access to assigned resources and policies. You can suspend or delete the user from this user state. Active users are billed as normal users.<\/li>\n<\/ul>\n\n\n\n
<\/p><\/div>Note:<\/strong> After a\u00a0new user is activated, the user must complete the onboarding process, including setting a JumpCloud password, logging in to the JumpCloud User Portal\u00a0and, if required, setting up identity verification\u00a0to use JumpCloud resources.<\/p><\/div><\/div><\/div>\n\n\n\n
- \n
- Suspended <\/strong>– Revoke a user\u2019s access to assigned JumpCloud resources or prevent a user from accessing resources. You can activate or delete the user from this user state. Suspended users are billed as normal users.<\/li>\n<\/ul>\n\n\n\n<\/p><\/div>
Note:<\/strong> Existing users do not need to take any additional steps when the user’s state is changed from Suspended to Active, and the users receive the same access they had prior to being suspended.<\/p><\/div><\/div><\/div>\n\n\n\n
User states are shown from the user\u2019s page, User\u2019s Details tab, and Highlights tab for a user from a User Group, Device, LDAP, Active Directory, Google Workspace Directory, and M365\/Entra ID.<\/p>\n\n\n\n
Managing User States<\/h2>\n\n\n\n
User states can be changed from Staged to Active, Active to Suspended, and Suspended to Active. A user cannot be changed back to a Staged user state once activated.
There are different ways to change a user state:<\/p>\n\n\n\n- \n
- Setting the default user state for new users to either Staged or Active is done from Settings<\/strong> > User Management<\/strong> > Default User State for User Creation<\/strong>. You can specify a different user state default for each user creation method.<\/li>\n\n\n\n
- Changing a user state to Active can be scheduled or done manually. Activating a user immediately gives that user access to all assigned resources and applicable policies in JumpCloud. <\/li>\n\n\n\n
- Changing a user state to Suspended can be scheduled or done manually. Learn more below.<\/li>\n<\/ul>\n\n\n\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\")
<\/p><\/div>Warning:<\/strong> Users can’t be changed back to Staged once they are activated.<\/p><\/div><\/div><\/div>\n\n\n\n
Setting a Staged User State<\/h2>\n\n\n\n
Considerations<\/strong>:<\/p>\n\n\n\n
- \n
- Staged users can\u2019t receive emails. When you change their user state from Staged<\/strong> to Active<\/strong>, you control whether or not an email is sent. The type of email sent (activation or welcome) is automatically determined based on whether or not a password has been set for the user.<\/li>\n\n\n\n
- A user state can’t be changed back to Staged <\/strong>once activated.<\/li>\n\n\n\n
- Staged users are not provisioned to AD.<\/li>\n<\/ul>\n\n\n\n
Assigning Resources to Users with a Staged User State<\/h3>\n\n\n\n
Users in a Staged user state can be assigned resources. See Connect New Users to Resources<\/a> to learn more about assigning resources.<\/p>\n\n\n\n
A staged user won’t have access to any assigned resources until their user state is changed to Active. The resource type will determine if a user account is or isn’t provisioned. The table below outlines the behavior.<\/p>\n\n\n\n
- A user state can’t be changed back to Staged <\/strong>once activated.<\/li>\n\n\n\n
- Setting the default user state for new users to either Staged or Active is done from Settings<\/strong> > User Management<\/strong> > Default User State for User Creation<\/strong>. You can specify a different user state default for each user creation method.<\/li>\n\n\n\n
- Active <\/strong>– Immediately provision a user account and enable a user\u2019s access to assigned resources and policies. You can suspend or delete the user from this user state. Active users are billed as normal users.<\/li>\n<\/ul>\n\n\n\n
- Single user creation through the API<\/a><\/li>\n\n\n\n
- Go to Users > Settings<\/strong>.<\/li>\n\n\n\n
- The default value you set for Settings<\/strong> > User Management<\/strong> > Default User State for User Creation<\/strong> > Manual\/Single User API<\/strong> is what will determine the default state for users imported from AD.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
- For users created in the Active<\/strong> user state, user emails are still determined by the method used to create a user in JumpCloud and the password status. See the Building Users section in Get Started: Admin Implementation<\/a> to learn more. <\/li>\n\n\n\n
![\"\"](\"https:\/\/jumpcloud.com\/wp-content\/uploads\/2023\/05\/Snag_174cf55b.png\")
<\/figure>\n\n\n\n