If you access the host page from a location that isn't blocked, download the client and copy it to a computer where the host page is blocked, it still works to connect to a session (until the access token expires). Would expect it to also block connecting to the session (but not relay traffic, as we connect to external users).

Grant a new permission or allow a higher privileged admin to remove the companies from role permissions for lower technicians. Need to allow my tier 2/3 techs full admin to CWC, but not allow them to see screenshot or remotely connect to CEO PC without consent to avoid engineer seeing confidential info.

We don't need the more advanced consent controls, we have permission, this is just to enhance interaction with end users.

If we are responding to a non-realtime user remote support request, we want to give them a few seconds to close sensitive documents they may have open, before we connect, as a courtesy.  
Ideally with a timeout you can configure right there, or a global default timeout.

For example, 5 minutes after they send an email requesting support, instead of a either needing to lookup and contact them, or a sudden "Your computer is being controlled by XXXX", they could get a "XXXX would like to remotely connect to your computer: Allow/Deny [Countdown].

Like the "Remote Control: Prompt for confirmation" option in Teamviewer. 

Then, if they don't respond, we can just use the regular Join option.

Per subject, have noted that the performance in Backstage has suffered dramatically since the new Shell was introduced.

Simple things such as opening the event viewer and scrolling are dramatically slower (i.e clicks not being registered for up to one second, using the cursor keys to scroll through event logs used to be instant but now there's a marked delay)

Have seen this across a wide stretch of hardware; doesn't seem to be hardware specific. An option to toggle between the original cmd/powershell and the new shell would be useful if this is something that cannot be resolved.

in order to use the remote diagnostic toolkit or execute commands in backstage we have to have the security control RemoveCommandFromSession allowed. This allows techs to remove commands they have issued from the script history. We need that history to remain and therefore would like to request that this no longer be required.

we need the transparency for supervisors to review as evidence that a team member did / did not execute commands.

When working with specific clients there are requirements that prevent any work being done on a non-viewable console. As such we need to disable backstage access to all computer managed under these types of contracts.

The backstage feature should be disabled at the computer level by a setting on the host computer to prevent any user, no matter their access or privilege, from accessing such feature.

EYOU

We need to be able to hide the timeline tab for a specific security group.