How to best use DirectLink account in our case?

CHoogerhuis

I've currently set up our DirectLink account to fit the Windows Server environment, and limited the view to just be the Windows devices. This is done to encourage the team to get used to using SolarWinds, so they do not have to bother with logging in. However, I'm also being tasked with building a NOC view. Until now, it's worked quite well, as I've just been using the Windows information. However, I'd like to add a network map in there. But due to the limitations placed on the DirectLink account, Cisco devices won't show. But if I add the Cisco devices into the permitted accounts, they also show up under the node view. Any thoughts on how edit the account/view limitations to a point where when using the DirectLink account the server team sees what they want, but when I use a NOC view, I can get network devices up there?

jm_sysadmin

I used to use the DirectLink account, I no longer use it. First, if you have the pass through authentication set up, they won't need to do any login. 
Configure automatic login in the SolarWinds Platform
I suggest setting up groups for access (or leverage existing ones) for the roles as you see it, and add that so its easy to manager users. Right now we are moving from AD auth to Azure AD auth. 

It can make the big TV screen a bit harder, but we simply have an application user for NOC setups with the appropriate permissions that get signed in with RDP/VNC/Dameware when needed. 

Don't fight it, leverage the users, you will someday want the audit trail.