{"id":60004,"date":"2022-03-08T10:18:18","date_gmt":"2022-03-08T15:18:18","guid":{"rendered":"https:\/\/jumpcloud.com\/?p=60004"},"modified":"2023-03-08T15:29:07","modified_gmt":"2023-03-08T20:29:07","slug":"best-practices-for-migration-of-device-permissions-from-a-user-to-a-group","status":"publish","type":"post","link":"https:\/\/jumpcloud.com\/blog\/best-practices-for-migration-of-device-permissions-from-a-user-to-a-group","title":{"rendered":"Best Practices for Migration of Device Permissions from a User to a Group"},"content":{"rendered":"\n
JumpCloud is the one-stop solution for centralizing access for users across devices, applications, directories, and endpoints. Customers can now manage privileged access and\/or permissions across multiple devices to ensure sensitive, administrative rights are maintained by leveraging the power of User Groups.<\/p>\n\n\n\n
JumpCloud enables administrators to manage permissions on devices requiring Administrator\/Sudo or Passwordless Sudo permission (the latter is only available on Mac and Linux). This allows administrators to have better control and visibility over who has access to which devices. Recently, JumpCloud released two new features that allow administrators to control these permissions at the User Group level, as well as per User Group to Device Group bind for more granular control. As a result, any user that\u2019s a member of the User Group automatically inherits permissions set at the group level.<\/p>\n\n\n\n
This best practices blog:<\/p>\n\n\n\n
There are four different ways a user can have Administrator\/Sudo permissions applied for a given device. The following illustration is a visual representation of how these permissions can be applied and\/or cascaded based on where the permission is configured.<\/p>\n\n\n\n
The administrator can choose any of these methods based on the organization\u2019s need to control individual devices and the roles the users will hold through the lifecycle of the identity.<\/p>\n\n\n\n