Limit Hosts to X number of open Sessions

Avatar
  • updated
  • Considering for Future Release

From CW#7560570:


Partner would like to limit ScreenConnect hosts to only be able to open a configurable number of sessions at a time, preferably with a way to have different users with different numbers of sessions that can be open (licenses used).

Duplicates 4
control amount of unattended licenses that a user can use

Currently if a user is created it can use the entire amount of licenses for unattended access that we have. So if we have 5 concurrent licenses on a self hosted and 3 different users. One user could open 5 unattended session with there login and no other users can then open a unattended session unless you kill one of those open unattended. When you have 500+ client machines finding the open ones can be difficult... Would be nice if we could set a control on a user to limit them to one session or multiple, but we choose the count.

Ability to limit the number of sessions a user can consume

I would like to define how many sessions a given user can consume, thereby reserving sessions for other users. I want to be able to define different session limits for different users. REALLY need this.

Limit number of active connections to specific techs

Would like to have the ability to limit tech A to 1 active connections at a time and tech B to unlimited number of active connections

Limit users to X number of open Sessions

It would be very helpful to be able to limit ScreenConnect/Connectwise users to only be able to open a configurable number of sessions at a time, preferably with a way to have different users with different numbers of sessions that can be open (licenses used).

Avatar
0
Tek Ease

Just came across the need for this today. I decided to open up my instance to another tech and he already didn't understand that he must ONLY have 1 active session at a time because it prevents me from doing my normal workflow with 2 or 3 other active sessions. I looked in the admin for a setting and none found, so I started Googling. +1 for this feature, please!

Avatar
0
anonymous

Hey All,

I don't have an ETA, but I can say we are actively working on this request. We've decided to go down the extension route, so keep an eye out on the Extension Spotlight forum. As soon as we finish development, and testing, the extension will be live. 

Thank you for your patience, and feedback! 

Avatar
0
Ryan Orme

is there any update on this or are we still waiting for this to be implemented? its been quite some time can someone from connectwise control update this???

Avatar
0
Stelios Ioannidis

Need this as soon as possible as my techs are eating up all the licenses at times.

Avatar
3
cps

Given that this was first requested four years ago and roadmapped a year ago, it seems it is not high priority for anyone at ConnectWise. Perhaps this will help: if you actually implement this I will buy more licenses. I have been refusing to buy more licenses until I can control usage, e.g., x number of licenses are available to user type A, y number are available to user type B, and all are available to user type C. Further, by constraining access for certain user groups, this will encourage those group leaders to purchase additional seats as well.

So, please get this feature off the schneid so we can send you some more money!

Avatar
0
Luca

Please give us an update on this.

Avatar
0
Chad Potter

Seems basic. Can we get this going?

Avatar
0
Virgil Turner

I love ConnectWise, and hate Team Viewer. Sadly I am forced to continue to work with clients using Team Viewer because this FUNDAMENTAL NECESSITY is missing from ConnectWise! Can you think of ANY other licensed-based solution where the vendor provides ZERO control over how many resources a single member of staff can consume? Can someone from ConnectWise dignify us all by explaining why this hasn't been addressed in nearly 5 years? 

Avatar
3
cps

Seriously, how hard can this be? Reading through this thread, apparently this is a request that has been ongoing since 2010, which is 10 years ago.

Here is your algorithm:

1. Add an admin-accessible field to the Roles record called max_open_sessions.

2. When a user attempts to open a session, check that user's Role's current open session count against max_open_sessions, and decline to open if the count is greater than that number.


It requires keeping track of the current number of open sessions for each Role, which again can't be too hard to do.

Does this really need an extensive re-design, or a complex extension, that is so hard that a decade is not enough time to get it done?



Top contributors

Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar