| Both sides previous revision Previous revision Next revision | Previous revision |
| technical:generic:account-audit-portal [2026-01-15 10:27] – [Account Audit Portal] frey | technical:generic:account-audit-portal [2026-02-09 17:48] (current) – [Edit user dispositions] frey |
|---|
| Most workgroup contacts possess an IT-RCI account, and that account should be used to authenticate on the audit portal. For example, the IT-RCI user ''trainf'' acting as contact on a workgroup should authenticate with the username ''trainf'' and the IT-RCI password. | Most workgroup contacts possess an IT-RCI account, and that account should be used to authenticate on the audit portal. For example, the IT-RCI user ''trainf'' acting as contact on a workgroup should authenticate with the username ''trainf'' and the IT-RCI password. |
| |
| Contacts who do **not** possess an IT-RCI account will have a UDelNet Id and password for central University systems (including email). In this case, the contact's email address and UDelNet password should be used to authenticate on the audit portal. For example, Betty Crocker is an administrative contact on workgroup ''chocochip'' but has no IT-RCI account; she should use her UD email address, ''crocker@udel.edu'', and UDelNet password. | Contacts who do **not** possess an IT-RCI account will have a UDelNet ID and password for central University systems (including email). In this case, the contact's email address and UDelNet password should be used to authenticate on the audit portal. For example, Betty Crocker is an administrative contact on workgroup ''chocochip'' but has no IT-RCI account; she should use her UD email address, ''crocker@udel.edu'', and UDelNet password. |
| |
| The portal exists at [[https://www.hpc.udel.edu/acct-audit/|https://www.hpc.udel.edu/acct-audit/]]. | The portal exists at [[https://www.hpc.udel.edu/acct-audit/|https://www.hpc.udel.edu/acct-audit/]]. |
| {{ :technical:generic:caviness_disposition_3.png?w=400 |}} | {{ :technical:generic:caviness_disposition_3.png?w=400 |}} |
| |
| **If all members of the workgroup should be allowed to access and modify the files**, choose "To the workgroup" from the menu. All files owned by the user on the file system in question will have their group ownership reassigned explicitly to the workgroup. | **If ownership should be transferred to the workgroup itself**, choose "To the workgroup" from the menu. All files owned by the user on the file system in question will have their group ownership reassigned explicitly to the workgroup. Note that this does not imply users will be able to read/write any of the files — see the next section on Fixup Permissions. |
| |
| **If a single user in the workgroup should be allowed to access and modify the files**, choose "To a specific workgroup user" from the menu and choose the target user from the menu that appears: | **If ownership should be transferred to a single user in the workgroup**, choose "To a specific workgroup user" from the menu and choose the target user from the menu that appears: |
| |
| {{ :technical:generic:caviness_disposition_4.png?w=400 |}} | {{ :technical:generic:caviness_disposition_4.png?w=400 |}} |
| == Fixup permissions == | == Fixup permissions == |
| |
| If the "Fixup permissions on reowned file/directories/" checkbox is checked: | If the "Fixup permissions on reowned file/directories" checkbox is checked: |
| |
| * **For reownership to the workgroup**, permissions will be altered to give the **group** read+write+execute | * **For reownership to the workgroup**, permissions will be altered to give the **group** read+write+execute |
| * **For reownership to a user**, permissions will be altered to give the **user** read+write+execute and the **group** no privileges | * **For reownership to a user**, permissions will be altered to give the **user** read+write+execute and the **group** //no privileges// |
| |
| If not checked, then the permissions will not be altered. | If not checked, then the permissions will not be altered. |