Admin User Management (3.x.x and earlier): Difference between revisions
| (16 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
User management can be accessed by all users from the drop-down arrow under log out in the top right corner. | User management can be accessed by all users from the drop-down arrow under log out in the top right corner of the screen. | ||
[[Image:UserOptions.png]] | [[Image:UserOptions.png]] | ||
| Line 34: | Line 34: | ||
[[Image: | [[Image:AddUserEnterPassword.png]] | ||
== Deleting Users == | |||
You can also delete users from the edit page. For security reasons, you must always enter your current user password before deleting a user. You will be prompted to confirm the delete action. | |||
'''Note:''' Deleting users can make tracking down who made changes more difficult. Consider making a user inactive instead. | |||
[[Image:DeleteUser.png]] | |||
== User Rights == | == User Rights == | ||
Rights are broken out into | Rights are broken out into these categories: ''Default'' (read), ''Write'', ''Admin'' and ''API Access''. In addition, as starting with Obsidian 2.0, ''Default'' read access can be limited using the ''Limited Read Access'' setting. | ||
''Default'' rights allow you read access to most parts of the application, with the exception of user lists and the [[Admin_System_(3.x.x_and_earlier)|System]] tab. | |||
''Write'' rights allow you perform most operations, with the exception of viewing and changing users, and the [[Admin_System_(3.x.x_and_earlier)|System]] tab. | |||
'' | ''Admin'' rights allow you access to view and change [[Admin_System_(3.x.x_and_earlier)|system settings]] and users. | ||
'' | ''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this role grants the ''Default'' read access to the admin application. | ||
'' | ''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that if a user has Write or API Access, this setting has no effect. | ||
Latest revision as of 17:02, 1 July 2016
User management can be accessed by all users from the drop-down arrow under log out in the top right corner of the screen.
User management allows all users to see their current rights. In addition, if native authentication is used, all users may change their password. Admin users may also view and manage users when native authentication is used.
Viewing Rights & Changing Your Password
Clicking My User will bring you to the page which lists your user rights. If native authentication is used, you may also change your password from this page.
Listing Users
Admin users may view current users, add users, and update settings and passwords of existing users. Clicking the User Setup link in the log out drop-down will list existing users, as will clicking List Users in the user navigation area below the navigation tabs.
Changing Users
Clicking a user in the table will bring you to the user edit page. From here you can make changes. For security reasons, you must always enter your current user password to make user changes.
Note: The question mark icon that appears next to the form title indicates inline help. Click on the icon to see help related to the current page.
When saving changes, you may receive error notifications. In this case, no changes were saved and you may correct your user setup and resubmit.
Note: When editing existing users, you may change their password by entering the new password and confirmation. If you leave both blank, the password will remain unchanged.
Deleting Users
You can also delete users from the edit page. For security reasons, you must always enter your current user password before deleting a user. You will be prompted to confirm the delete action.
Note: Deleting users can make tracking down who made changes more difficult. Consider making a user inactive instead.
User Rights
Rights are broken out into these categories: Default (read), Write, Admin and API Access. In addition, as starting with Obsidian 2.0, Default read access can be limited using the Limited Read Access setting.
Default rights allow you read access to most parts of the application, with the exception of user lists and the System tab.
Write rights allow you perform most operations, with the exception of viewing and changing users, and the System tab.
Admin rights allow you access to view and change system settings and users.
API Access grants the user the ability to use the full REST API. In addition, this role grants the Default read access to the admin application.
Limited Read Access prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that if a user has Write or API Access, this setting has no effect.
