The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.



Go to last post Go to first unread
#1 Posted : Friday, June 19, 2015 9:01:57 PM(UTC)

Rank: Member

Joined: 4/20/2015(UTC)
Posts: 14
United States

So far I am making this work just fine to allow access to different techs to control and help customers out base off their log in level and access level.

The problem I am running into to make this even easier is that under the security settings - there are tons of "allow/view" but no option to "block/hide". I know that sounds backwards, but with the way I have things - or would like to make things - I will need a "NOT".

For example, I have screen connect showing different companies under the Access menu. From there I track assign users and their security level.

From there, I block access to "all-access" and then assign each sub menu to the tech level I want them to be able to access to. This takes a lot of time. I have to update the access each time I add a new company.

Instead of allowing every sub menu to be seen - I like to go a head and have it show all the menus and just hide a selection of these instead: *NOT* ViewSessionGroup: 'CompanyName'

Hope this is clear. If you have questions, please let me know.

Edited by user Friday, June 19, 2015 10:57:37 PM(UTC)  | Reason: Not specified

#2 Posted : Tuesday, June 23, 2015 4:50:42 PM(UTC)

Rank: Administration

Medals: Level 3: Shirt off your back! Received 25 Thanks!

Joined: 5/30/2012(UTC)
Posts: 501
Location: Raleigh, NC

Thanks: 56 times
Was thanked: 82 time(s) in 68 post(s)
Thanks for your submission. I'll be sure to log your request.
ScreenConnect Team
#3 Posted : Wednesday, June 24, 2015 4:06:09 PM(UTC)

Rank: Member

Joined: 5/19/2015(UTC)
Posts: 17
United States


Would be useful to have a "RequireGuestConsent" instead of "HostSessionWithoutConsent", so I could allow it for all machines except those groups. I have over 100 groups that change often, so it's easier to require consent for one group instead of adding "HostSessionWithoutConsent" for all but those couple of groups.

Edited by user Wednesday, June 24, 2015 4:17:09 PM(UTC)  | Reason: Not specified

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.