I removed access from a user from Risk Cloud. What happens to their assignments?
If a user is deactivated, will they be unassigned from Records?
No. In order to allow users to be easily deactivated and reactivated without losing previous assignments, users will not be unassigned from Records when they are deactivated. In order to unassign a user from a Record, you should use the Pencil Icon to assign it to another user that has access to the Record or make the Record unassigned.
Please note: The Records Report can be used to review records that are currently assigned to a user in an application by entering the user's name or email address into the search field.
A user no longer has access to a Step, but they are still assigned to a Record in that Step. Why is that happening?
If a user was previously assigned a Record and, after that assignment, had their access removed from the Step where that Record resides, the user will not be unassigned from that Record and will be able to continue editing the Record. Similar to the above, a user would need to be unassigned from the Record via re-assignment to another user that does have access to that Step or unassignment. Once unassigned, the user will no longer be able to view or edit the Record based on the access they have been granted.
A user has been deactivated and/or they are no longer included in a Permission Set or Role that allows them to be chosen from a User Field. Will all Records where they were previously populated in that User Field be cleared of their name?
No. For historical purposes, users' names will not be cleared from User Fields on Records where they are populated if a user is deactivated or removed from the Role or Permission Set assigned to the User Field. However, when a user is deactivated or removed from a Role or Permission set assigned to a User field, they will no longer be selectable in the drop-down on the form.
If a user is deactivated, will they be removed from Roles and/or Permission Sets?
No, users will not be removed from Roles and/or Permission Sets when they are deactivated. Similar to the above, this is to allow users to easily be reactivated without forcing the Risk Cloud administrator to re-assign appropriate access.