|
|||
|
6.1 User ManagementFebruary 16th, 2026 RBAC required: bear: User administration BEAR admin users are created and managed according to RBAC1 to restrict them to specific admin tasks for specific applications. Each application has its own specific RBAC roles which are made available to BEAR for purpose of granular permission management for each user. There is one master root user which has access to everything. This user cannot be deleted but ideally should not be used for day-to-day administration tasks. Upon deployment, it is best practice to create at least two specific named administrator users and only use the master root account if all other users with the bear: Root access role are incapacitated. There is no limit to the number of admin users that can be created. 6.1.1 Creating a New User Account
You can easily create a user with the same RBAC roles as another user by using the Copy Roles field and inputting the name of a user you wish to use as a template.
6.1.2 Viewing All User AccountsTo view all users and their full profile at once, simply select the Users tool group from the Admin Tool menu and then select the View tab.
6.1.3 Modifying a User Account Profile
New account settings will only take effect when the user next logs in. Current sessions will not be affected or interrupted. 6.1.4 Locking/Unlocking a User AccountUser accounts should be locked or unlocked using the steps described in Modifying a User Account. 6.1.5 Resetting a PasswordA password reset involves an automatically generated password being sent to the user's registered address. They should be encouraged to change this again after they log in.
6.1.6 Deleting a User Account
There is no confirmation prompt for deleting users. Be careful to review your selection before deleting. 1 Role Based Access Controls
|
||