ScreenConnect > Administration > Advanced > Other Settings: Is User Allowed to Require Consent <-- SET PER SITE, NOT ROLES

Avatar
  • updated
  • Pending Review

We want to ONLY turn on the following option for SPECIFIC sites, NOT ROLES:

ScreenConnect > Administration > Advanced > Other Settings:

Is User Allowed to Require Consent

Enables the "Require Consent" toggle in the guest client UI

Avatar
0
mark tetuan

We use ScreenConnect integrated with ConnectWise RMM.

No, SessionGroups are not the answer. Please refer to ConnectWise case# 03244684.

Please reach out to me.

Avatar
0
mark tetuan
Quote from Sean White

The 'best' way to enable consent is at the session group level and requiring Consent on connection on a per role basis. However, it sounds like you have a different use case, can you explain what you mean on a per site basis?


The option you are referencing is part of an app.config and currently it is a global setting. We are investigating ways to make this available on a per-endpoint basis, but at this time, I do no ETA on when we will wrap up the investigation and implementation.


Yes, per site would mean configuring the "Is User Allowed to Require Consent" setting for a given site and its associated computers.


For example, if I had a site called "CompanyABC" and it had 5 computers, and another site called "CompanyXYZ" and it also had 5 computers, I could apply the "Is User Allowed to Require Consent" setting ONCE for "CompanyABC" and it would ONLY affect the 5 computers for "CompanyABC," and not the other 5 computers at "CompanyXYZ."

Configuring at the site level, would save time by only having to apply the setting once for a site instead of 5 times to configure each computer.

Avatar
0
Sean White Team Member

The 'best' way to enable consent is at the session group level and requiring Consent on connection on a per role basis. However, it sounds like you have a different use case, can you explain what you mean on a per site basis?


The option you are referencing is part of an app.config and currently it is a global setting. We are investigating ways to make this available on a per-endpoint basis, but at this time, I do no ETA on when we will wrap up the investigation and implementation.