How Do I Troubleshoot Session Policies?
Session policies can be applied to multiple objects within the same session. Because layering policies can be complex, you can use the Session Policy Simulator to determine what the outcome will be. Additionally, you could use the simulator to troubleshoot why a permission is not available when you expected it to be.
To access the session policy simulator, navigate to /login > Users & Security > Session Policies. Scroll to the bottom of the page.
Start by selecting the representative performing the session. This dropdown includes user accounts, embassy user accounts, and rep invite policies.
Next, select the session start method. This can be one of Public Portal, Bomgar Button, Jump Client, Jumpoint, or Local Jump.
If you selected Public Portal, choose the public portal to use for this simulation of an ad-hoc session.
If you selected Bomgar Button, search for a deployed Bomgar Button by profile, associated public portal, associated queue, computer name, or description. The associated public portal will be automatically selected above.
If you selected Jump Client, search for a pinned Jump Client by name, comments, queue, group, or associated public portal. The associated public portal will be automatically selected above.
Because local Jumps and Jumpoints are always associated with the default public portal, there are no further settings to define.
Click Simulate. In the area below, the permissions configurable by session policy are displayed in read-only mode. You can see which permissions are allowed or denied as a result of the stacked policies, as well as which policy set each permission.