{"id":74818,"date":"2023-05-18T10:26:22","date_gmt":"2023-05-18T14:26:22","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=74818"},"modified":"2023-10-12T17:21:23","modified_gmt":"2023-10-12T21:21:23","slug":"connect-new-users-to-resources","status":"publish","type":"support","link":"https:\/\/jumpcloud.com\/support\/connect-new-users-to-resources","title":{"rendered":"Connect New Users to Resources"},"content":{"rendered":"\n
All resources in JumpCloud are implicitly denied, which means that by default, new users don’t have access to a resource endpoint until they are explicitly connected to it directly or through group membership. You can bind the user to any of the resources connected to JumpCloud from a device to applications, networks, etc. If the user is created in a Staged user state, they won’t gain access to their assigned resources until they’re activated. See Manage User States<\/a> for specific information about when a user is provisioned or assigned resources.<\/p>\n\n\n\n Prerequisites<\/strong>:<\/p>\n\n\n\n Access to resources may be granted by connecting a user to any of the following:<\/p>\n\n\n\n Binding a user to a group of users is an organizational construct. No access is granted until that group has been bound to a resource. You can edit group membership in this view. <\/p>\n\n\n\n Binding\u00a0a user directly to a device is good practice if this will be a one-to-one relationship. For example, a single user is bound to their work device to which no one else can have access. A user bound via a (user) group can also be bound directly to the device to enable a custom permission to be set on only that device. UI behavior for group and direct connection is explained further in\u00a0Get Started: Devices<\/a>.\u00a0When a user is bound to a device, it either creates a new local user account or\u00a0takes over an existing account\u00a0of the same username. See Take Over an Existing User Account with JumpCloud<\/a>.<\/p>\n\n\n\n You can also let new users provision their account to macOS and Windows devices directly from the login screen. See Provision New Users on Device Login<\/a>.\u00a0<\/p>\n\n\n\n This can include Google Workspace, Microsoft 365, and\/or JumpCloud LDAP. These resources are generally accessed by groups of people. So binding directly to the user, while possible, isn’t generally recommended. Rather, bind the user to a group that has already been granted access to the directory. A direct connection can’t be made if the user is already bound to the resource via a group of users.<\/p>\n\n\n\n\n
User Bindings<\/strong><\/h2>\n\n\n\n
\n
User Groups<\/h3>\n\n\n\n
Devices<\/h3>\n\n\n\n
Directories<\/h3>\n\n\n\n