Ability to stop users from kicking other users off of a support session

It would be nice to search / filter within the Appearance Tab for both Web Resources and Client Resources. 

I'd like to be able to put the Computer Info pane back underneath the Sessions.  We were a long time user of 5.4, which had the layout situated that way.  

If we could toggle between situated on the right hand side, versus the bottom, that'd be great!

The Zendesk integration extension is pretty awesome but it is lacking a very important feature to have an option to automatically end and delete a support session when a zendesk ticket is solved or closed,

When i'm creating a support session from the connect wise web portal I usually delete it when i'm done, but most of the time i create sessions using the zendesk connect wise application (extension)  through zendesk web portal, and when I solve the ticket the sessions stay open in screen connect, I then have to login to screen connect figure out what sessions are no longer needed and delete them manually.

Please consider adding a feature to the extension,

Thanks.

A way for users to query their timeline for a given range, ex a week. Would aid in time entry when you may have forgotten what day you were connected to a machine.

We would feel much better if we knew our database maintenance is being completed.  Aside from me looking at the info I have no way to know what has been configured has been completed.  Dealing w/ server backups for 20 years I'm not about to just trust an automated task is doing its thing properly.  Perhaps there is currently an Event.EventType I can use to trigger this?

Thanks

Dave

The ability to hide the screenshots within the 'Join Session' dialog that comes up after a client types in a code would be nice since we get customers that will attempt to click on the pictures themselves unfortunately. It's pretty easy to walk a customer through clicking on the download then clicking run. I'm fine with the text but it is pretty frequent we get not-so-savvy customers that will insist they are running the application and clicking on it when they are clicking on the images themselves. It just leaves room for confusion for people that can't distinguish the screenshots from their computer.

Store the config file in %appdata% rather than programdata. This means that users logging onto the same machine do not overlap their settings (pinned windows etc.) - for example, on terminal servers.

When we create a support session from our ScreenConnect web UI (for on-demand support), it auto-generates a four-letter code for the client to connect. We would like the option to have this generate a number code instead, which would be easier to provide clients over the phone rather than having to spell out letters using phonetics.

Currently the session filter options are primarily limited in detail based on the guest device. I need the ability to filter and link information based on host/staff information. For example, the following session filters could easily provide significant value to distributed enterprise environments:

Local:

GuestNetworkAddress = HostNetworkAddress

This group would show all devices on the logged in users currently active network. For traveling techs, this could save quite a bit of time. Low-level techs and onsite staff could be assigned only this group for visibility to easily group only those devices they need access to at that time.

Enterprise/Vendor Domain rules for filtering:

GuestLoggedOnUserDomain = HostLoggedOnUserDomain

  or

GuestMachineDomain = HostMachineDomain

Other host/staff details could be exposed for additional benefit. For example, "HostRole", "HostOrganization", and it would be awesome if we could have variable field input for user accounts meta information, the same as devices. HostCustomPropertyN, for example. This would allow far broader controls for grouping and permissions.

Much of this is possible through workarounds using Notes, but imagine the power of using custom property fields for staff to associate things like GuestOperatingSystemName for those staff that are only skilled in a specific OS.