UI Design - DRS | Document Record Enhancements

The following items were identified during discussions with staff and will need additional discovery and design.

**1. Delete document from a document record**
* Design the deletion document action
* Design the restricted access state for staff without permission
* Pending requirements from the BA @oanyahuru

**Note from Doug:** For DRS record deletion, the solution depends on the number of staff with the admin role. It should really be in keycloak as a new role tied to the user login. If the set of users is small the DRS API can maintain the admin user - keycloak is more work to set up and maintain. Access would be assigned manually with both options.

Open question: Which staff roles should have access to remove documents?

**2. Rescan of a document**
* Design the rescan workflow _(Reach out to Taylor)_
* Design confirmation, success, and error states

**3. Documents Section**
* Replace the current card layout with a table view
* Update the download component

**4. Page count discrepancy workflow**
* Map the current workflow
* Design notification and resolution workflows

-------

Scanning App Flow provided from Taylor: