Contents
Why should you create users as standard users rather than Administrator users?
A Standard User Account is more secure and recommended for everyday tasks like launching and using apps, browsing the web. An Administrator account is best as a backup account for Administrative task like installing applications, updating the system.
What is the difference between Administrator and standard user account?
Administrator accounts for users who require full access to the computer. Standard user accounts for those users who need to run applications but who should be limited or restricted in their administrative access to the computer.
Which is better standard user or administrator?
Can a user account be used as an admin?
The support team is logged into their regular machines with their user account, but uses a virtual machine logged in with an admin account that has admin tools such as sharegate, sharepoint designer, etc. So any browser on the VM is using the admin credentials.
It can be done using session. When a user login, save it as Session [“User\\ and for admin Session [“Admin\\. it means your button will be visible only when login will be with admin session.
Is it good to have admin users in the same table?
You would have to make sure that one type of user id could never be accidentally used as the other type. It’s harder to spot a problem like that, than spotting something that could cause a user id changing into a different user id.
Are there drawbacks to separate user and admin accounts?
There were a few replies that mention separate user and admin accounts for the people doing the administration, but I was hoping to get a conversation more focused on that. A drawback that comes to mind immediately is the cost of extra licensing for the admin accounts. Are there other drawbacks? What benefits are you seeing with this structure?