Some app.config settings on a per user basis

Avatar
  • updated
  • Considering for Future Release

I'd like to see more settings available on a per-user rather than per-endpoint basis. One example:


I use SC to do remote support for my clients. I'm almost always connecting in when they're there, so I never want to blank the monitor. I've provided access to SC for a client who wanted access to their own PC, so i created a user, customproperty with their name to give them access to their PC only, all that jazz. They can log in and use SC to connect to their PC and only their PC. They want the ability to blank on connect by default because they'll only be connecting to their PC when they're out of the office, so they don't want anyone snooping around and looking at what they're doing remotely. However, this is the same SC install on their PC that I connect in to when I support them while they're in the office, so I don't want it to blank. Setting the app.config on their computer would make it so that no matter who connected, they'd get blanked, which isn't ideal. If the preferences were attached to the user, then they'd get the blanking default they wanted, no matter the computer they connect from or into, and I'd get my non-blanking that I want.

Duplicates 2
Change "Share Clipboard" Default by user

I know it is possible to change the default of this setting (attached). But basically we have multiple admins. I personally use the clipboard all the time, which is why our default is to have it on start, but there are other admins who support users that the clipboard gets in the way. Can we have this set up on a per account basis?

Image 1045

Be able to apply app.config settings by the user/permissions

Have a choice to have seperate app.config settings apply to different users, useful for disabling commands

Avatar
0
Caitlin M Barnes Team Member
  • Under Review
Avatar
0
Caitlin M Barnes Team Member
  • Considering for Future Release
Avatar
0
Brandon Wilcox

We are also looking for a solution for this issue. Our use case is slightly different, but the need to customize the session by computer or user is there. 


We want Administrators (supervisors or management) to be able to connect "incognito", meaning no banner, pop up notification, suspended input, etc. 

We do not want all Hosts (technicians) to have this ability. 



Top contributors

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