Considering for Future Release
Control Access to toolbox items in security. or create separate toolboxes and assign per group
mhighsmith 7 years ago • updated by Jen B. 3 months ago • 11 • 1 duplicate
would like to have the ability to assign a certain set of tools to different users. A separate toolbox per security groups
Available in Version:
Customer support service by UserEcho
example: out internal MIS support does not need the same tools as our external POS Support.
This is alot like i was asking in creating groups for access to the tools in the toolbox.
For tools to be controlled properly, it would be essential to have the option server side, to completely disable Personal Toolbox functionality on all connected Host clients, so Support Teams don't run anything they like on Guest machines.
yes a version control would also be nice.
This is concerning from a security stand point for any user with access can store anything in their toolbox and there doesn't seem a way to ensure the tool version is current or even vetted...and not an application that was compromised and never updated.
If this get done, since you will be reworking the tool box, also have different tool box for standard session and backstage session would be great. The tools use in those 2 type of session vary greatly.
I would like the ability to hide the toolbox entirely for users we are selling remote access to.