Recommended Steps to Implement Jump Technology
When working with Jump Technology, there are a lot of moving parts. Here is a recommended order of implementation to make full use of your software.
- Add Jump Item Roles. Jump Item Roles determine how users are allowed to interact with Jump Items. These roles are applied to users by means of individual account settings, group policies, and/or when added to Jump Groups. For more information about Jump Item Roles, see Use Jump Item Roles to Configure Permission Sets for Jump Clients.
- Add Jump Policies. Jump Policies are used to control when certain Jump Items can be accessed by implementing schedules, sending email notifications when a Jump Item is accessed, or requiring approval or user entry of a ticket system ID before a Jump Item may be accessed. Jump Policies are applied to Jump Items upon creation and can be modified from the access console. Additionally, Jump Policies can be applied to users when associating a user or group policy with a Jump Group. For more information about Jump Policies, see Create Jump Policies to Control Access to Jump Clients.
- Add Jump Groups. A Jump Group is a way to organize Jump Items, granting members varying levels of access to those items. Users are assigned to Jump Groups either individually or by means of group policy. For more information about Jump Groups, see Use Jump Groups to Configure Which Users Can Access Which Jump Clients.
- Deploy Jump Clients. Jump Clients can be deployed to Windows, Mac, and Linux systems and do not require those systems to be on a network. Jump Clients are deployed from /login > Jump > Jump Clients. When creating the installer in the mass deployment wizard, be sure to set the Jump Group and Jump Policy to determine who can access the Jump Client and with what restrictions. For more information about Jump Clients, see Deploy Jump Clients from the Administrative Interface.