Teststand configurations based on windows login

[RaviShrigiri]

Presently we can login into Teststand using the windows login. Carrying this forward it will be good if all Teststand configurations ( ex report type,process model,search directories) are user specific.

This will need maintaining separate config files for each user.

On start Teststand will check the windows user name logged in and accordingly copy relevant config files and configure the Teststand.

[RayFarmer]

I can not see how this could be a good thing. On a production line you wouldn't want one operator running a different process model....

[RaviShrigiri]

The settings/configurations for an operator will be done by administrator only.Operator just logs in as operator without any privileges to change the settings.

Besides production line there is also scope for validation group.

[warren_scott]

I can see how this would be valuable for SOME areas, but for MY USE we want to never allow anything like this -- we want to make sure that everyone who logs into the system (wether an operator user or an administrator) gets the exact same report configuration, DB configuration, search paths, etc.  So if this gets implemented, make sure we can do something to "un-configure" the feature.

[RaviShrigiri]

I totally agree with you.This can be an optional feature.

[WireWeaver]

I'm declining this idea due to lack of community support. Since the introduction of Environments, there actually may be a reasonably simple workaround for this by giving each "user" their own environment by linking it in the shortcut on their desktop with the /env command:

https://www.ni.com/docs/en-US/bundle/teststand/page/choosing-an-environment.html