With most remote support software, every session is the same. Either you can control the remote computer, or you can’t. Bomgar, on the other hand, gives administrators more than 50 permissions to define how reps, customers and remote systems interact at a very granular level.
Bomgar's support session policies are dynamic, rather than rigid, bringing additional flexibility to already-powerful security measures. Admins can customize support session permissions to fit a variety of support scenarios.
Support session policies let you change the permissions allowed in a remote support session based on the support portal the customer came through or even the specific endpoint being supported.
Your support organization serves a variety of customers and business units, each with its own requirements around remote support
Some customers want you to resolve their issues as quickly as possible. They may want you to start support sessions with full remote control enabled.
Other customers are more concerned about security and defined proceedure. They may prefer you start support sessions in view only mode and prompt for permission before taking any action on their systems.
Bomgar Support Session Policies let you accomodate the needs of both groups by defining portal-specific permissions for each client.
Bomgar Jump Clients give you remote access to computers and servers.
When you use Jump Clients to access servers and backend systems, you want to launch right into remote control. No one is present on the other end of a server for you to interrupt. But when you access remote desktops, you may want to display a prompt in case an end-user is present.
That’s why Bomgar’s Support Session Policies let you define how a session begins based on the endpoint being supported.
With policies at the Jump Client level, you can choose to display a prompt if the remote desktop is one at which an end-user may be present. If the endpoint is a server, you can set the session policy up with no prompt.
Learn more about using Jump Clients for remote access.
You can also assign session policies to support representatives. Representative policies can impact attended sessions, where an end-user is expected to be on the remote desktop, or unattended sessions, which usually involve servers, point-of-sale systems, kiosks or un-manned remote desktops.
You can define policies for attended and unattended sessions separately. Attended session policies apply to ad-hoc screen sharing sessions and sessions started via Bomgar Button. Unattended session policies apply to sessions started through a Jump Client, Jumpoint, or local Jump.