|
1 | 1 | ---
|
2 | 2 | id: '1LTusqsZZWBwb5luysWoX59iHdj6vpnDi3hwYnu6ikPo'
|
3 | 3 | title: 'Access Control - Adding, Deleting, Editing Users'
|
4 |
| -date: '2024-10-16T17:10:20.012Z' |
5 |
| -version: 248 |
6 |
| -lastAuthor: 'janderson' |
| 4 | +date: '2025-03-12T16:15:21.056Z' |
| 5 | +version: 280 |
| 6 | +lastAuthor: 'anichols' |
7 | 7 | mimeType: 'text/x-markdown'
|
8 | 8 | links:
|
9 | 9 | - 'access-control-quick-add-multiple-active-users.md'
|
10 | 10 | - 'setting-up-e-prescribers.md'
|
| 11 | + - '../security/security-role-settings.md' |
11 | 12 | - 'https://mie.talentlms.com/shared/start/key:LTZIDNHR'
|
12 | 13 | source: 'https://drive.google.com/open?id=1LTusqsZZWBwb5luysWoX59iHdj6vpnDi3hwYnu6ikPo'
|
13 | 14 | wikigdrive: '0008bcbb1563384efe0a28ada6f97e9432e65f10'
|
14 | 15 | ---
|
15 |
| -Must have security permissions to be able to add/edit/delete users |
| 16 | +Must have security permissions to Manage Users and Manage Permissions to be able to add/edit/delete users and configure user security role exceptions, etc. |
16 | 17 |
|
17 | 18 | ## Search if a User Exists in the System
|
18 | 19 |
|
@@ -69,7 +70,7 @@ When adding a user, fill out all the fields you can:
|
69 | 70 | ### Edit User Screen
|
70 | 71 |
|
71 | 72 | * <strong>Username</strong> (first initial and last name all together and in lowercase) This will be their login name.
|
72 |
| -* <strong>Alias:</strong> Anything typed here will be shown in the authored by field of any document created/uploaded and printed/faxed etc. Sometimes a client or user doesn't want their full name to show in document headers or in stored documents, etc so they enter either only their first name here, or initials here, etc. The Authored By field looks and pulls the alias field first. If nothing is entered in the alias field, it will pull the user's full legal name. The below screenshot is an example. Example: Albert Aorta does not have anything entered into his alias field, so any document he creates, indexes, uploads, etc is stored by his full name. Example: alex someone who entered <em>alex</em> in for their alias field and {{% system-name %}} stores documents created by this person, uploaded, indexed, etc by his/her alias name/field since something is entered into that field. |
| 73 | +* <strong>Alias:</strong> Anything typed here will be shown in the authored by field of any document created/uploaded and printed/faxed etc. Sometimes a client or user doesn't want their full name to show in document headers or in stored documents, etc so they enter either only their first name here, or initials here, etc. The Authored By field looks and pulls the alias field first. If nothing is entered in the alias field, it will pull the user's full legal name. The below screenshot is an example. Example: Albert Aorta does not have anything entered into his alias field, so any document he creates, indexes, uploads, etc is stored by his full name. Example: alex someone who entered alex in for their alias field and {{% system-name %}} stores documents created by this person, uploaded, indexed, etc by his/her alias name/field since something is entered into that field. |
73 | 74 |
|
74 | 75 | 
|
75 | 76 |
|
@@ -161,21 +162,57 @@ Once your results produce, click on the underlined username (on the left column)
|
161 | 162 |
|
162 | 163 | Below this section of the username screen, it will display what departments the user is a member of, any restrictions, security exceptions, etc.
|
163 | 164 |
|
164 |
| -If you edit an existing user's security role (if you change the security role they are currently set to), when you submit your edit in their username screen, you may see a prompt box. If the user has any existing security role exceptions set, it will prompt if you want to keep their security role exceptions that are set, or if you wish to delete them and set the user to the security role settings that are default to that role you are changing them to. |
| 165 | +## Security Role Exceptions |
165 | 166 |
|
166 |
| - |
| 167 | +Users can be set to customized security permissions. The user is set to a security role when configured in the system. Security Roles are set to specific permissions for the entire default ‘role' in the system. However, individual users can have further customized security permissions or what we call ‘Security Exceptions'. |
167 | 168 |
|
168 |
| -You can also select options at the top of this user's summary. |
| 169 | +Security Role Exceptions are security permissions that are set differently than the overall security role the user is set to have. |
169 | 170 |
|
170 |
| - |
| 171 | +To customize an individual user's security, while in the edit user screen, the Customize User Security hyperlink is available. For more information on security role permissions or how to edit, please see the [Security Role Settings](../security/security-role-settings.md) guide. |
| 172 | + |
| 173 | + |
| 174 | + |
| 175 | +### Visibility to Security Role Exceptions set on a User |
| 176 | + |
| 177 | +Visibility to a user's security role exceptions are visible from Access Control in two areas: Access Control user search and View User screen. |
| 178 | + |
| 179 | +#### Access Control User Search |
| 180 | + |
| 181 | +From Access Control, search for a specific user. Once the user results in the output, you will see a column titled *Security Role Exceptions*. You can use the datavis grid to move this column to the position you wish and can save perspectives etc. |
| 182 | + |
| 183 | + |
| 184 | + |
| 185 | +Within the Security Role Exceptions column, Details hyperlink will appear **if** the user has any security role permission exceptions set on them. |
| 186 | + |
| 187 | + |
| 188 | + |
| 189 | +Click on the Details link to pop-up a list of any specific security role permissions that are an ‘exception' to what their default security role has set. Security role exceptions that display in this pop-up are what the user is currently set to, that is different from what their default security role is set to. |
| 190 | + |
| 191 | + |
| 192 | + |
| 193 | +#### View User Screen |
| 194 | + |
| 195 | +From Access Control, search for a specific user. Once any matching users listing results in the datavis output, you will see a column titled *Username*. You can use the datavis grid to move this column to the position you wish and can save perspectives etc. |
| 196 | + |
| 197 | + |
| 198 | + |
| 199 | +Click on the specific user's unique username (hyperlink) to advance to the *View User* screen. |
| 200 | + |
| 201 | + |
| 202 | + |
| 203 | +From this *View User* screen, scroll down to about the middle of the entire screen to see any specific security role permissions that are an ‘exception' to what their default security role has set. Security role exceptions that display in the View User screen in a section *Security Role Exceptions*. These security role exceptions listed here (if any) are what the user is currently set to, that is different from what their default security role is set to. |
| 204 | + |
| 205 | + |
171 | 206 |
|
172 | 207 | ### Options
|
173 | 208 |
|
174 |
| - |
| 209 | +There are several options when in the View User screen. |
| 210 | + |
| 211 | + |
175 | 212 |
|
176 | 213 | #### Edit User
|
177 | 214 |
|
178 |
| -If have security role permission to manage users, this link will appear. |
| 215 | +If you have security role permission to manage users, this link will appear. |
179 | 216 |
|
180 | 217 | Can click this to make changes to the username information screen and then click *Submit Edit* at the bottom.
|
181 | 218 |
|
|
0 commit comments