We want to have a small number of System Administrators whilst allowing for many more User Administrators.
We should separate out System Admin from User Admin in BC.
Create user account
Search for user account
Actions
Assign Company
Assign Role
Change Password
Deactivate (User)
Edit Authentication
Edit Details
Edit Preferences
Force Password Change
New Mail Address
Rename
Unlock documents
Upgrade an External User to a Full User
View Admin Reports | Recent User Report
Retire a user
Give bags
Change another Administrators password.
Do anything else outside of Access Management.
Change Access Rights.
Practical use of functionality?
A company needs to devolve the responsibility for add a departments users to user admins within the department. |
|
What is the impact of not doing this?
Owner/operators and large contractors need to be able to devolve user admin across their business (e.g. divisions or departments). |
I agree there should be another level, however the list above is far too much access. Anyone using IMS or Corporate account doesn't want people being able to change passwords. I think this level needs to be more like the following, and this is higher than I would like. I wouldn't want people changing anything to do with accounts that should be admin only as they can access the corporate/IMS information, so this is as far as a concession for this large contractor to go.
Search for user account
Actions
Edit Details
Edit Preferences
New Mail Address
Unlock documents
View Admin Reports | Recent User Report