Badger Data Access: Pushed Back and Denied Requests

Approvers may approve, deny, or push a request back to the submitter for updates or clarification.

Pushed Back Requests

If a workflow is pushed back by a Supervisor or Divisional approver, the user may make any necessary adjustments to justification, classification, row level, and/or expiration date. Once re-submitted, the workflow restarts and routes back through the Supervisor approval step.

If a workflow is pushed back by a Domain Steward (or delegate approver), the user may make any necessary adjustments to justification, classification, row level, and/or expiration date. Once re-submitted, the workflow routes directly back to the same Domain Steward (or delegate approver) who issued the pushback, bypassing prior completed approval steps.

Note: Only roles included in the original request may be adjusted or deleted when a workflow is pushed backwards. For changes to the subdomain or to include additional roles, please submit a new request.

Requests Pushed Back by Supervisor or Divisional Approver

1. When an approver pushes back the workflow for a request, the user will receive an email notification that it was pushed back and requires clarification.
   
   
   
   
2. Click the link provided in the email to access the request.
   
   
   1. Requests that have been pushed backwards by a Supervisor or Divisional approver may also be accessed in the Pushbacks section at the top of the My Roles landing page. Click the Update button to make changes.
      
      
      
      
3. Review the Reason for Pushback and make adjustments as necessary
   
   
   1. Click the Pencil button to edit the Classification, Row Level Security and/or Expiration Date for a corresponding Domain/Subdomain.
      
      
      
      
   2. If the request includes multiple domains and you need to remove one, use the trashcan icon on the corresponding row to delete it.
      
      
      
      
   3. If you decide the request is no longer relevant and you do not wish to make changes and resubmit, you may click “Delete Entire Request” to terminate it.
      
      
      
      
4. Adjust the Classification Level, Row Level Security, and/or Expiration as necessary.
   
   Note: Row Level Security represents which rows on the views will be returned for this subdomain. Currently only the University level is available for selection for all data roles. Row Level Security applies to Data access only. It does not apply to requests for Technology access and will remain blank in those instances.
   
   
   
   
5. Append to the Justification as necessary and click Submit.
   
   
   
   
6. The request will be routed to your Supervisor to begin the approval process again.
   
   
7. You can monitor the status of each Role ID included in the request on the My Roles landing page in the Pending Data Access Roles section.
   
   
   
   
8. You will receive an email notification when the request has passed all required approvals.

Requests Pushed Back by Domain Steward

1. When a Domain Steward (or delegated approver) pushes back the workflow for a request, the user will receive an email notification that it was pushed back and requires clarification.
   
   
   
   
2. Click the link provided in the email to access the request.
   
   
   1. Requests that have been pushed backwards by a Domain Steward (or delegated approver) may also be accessed in the Domain Steward Pushbacks section at the top of the My Roles landing page. Click the Update button to make changes.
      
      
      
      
3. Review the Reason for Pushback and make adjustments as necessary
   
   
   1. Click the Pencil button to edit the Classification, Row Level Security, and/or Expiration Date
      
      
      
      
   2. Make adjustments to Classification Level, Row Level, and/or Expiration Date.
      
      
      
      
   3. If you decide the request is no longer relevant and you do not wish to make changes and resubmit, you may click the trashcan icon next to the role to terminate the request.
      
      
      
      
4. Use the Comments box to send a comment back to the domain approver or to elaborate on the original Justification for access. Then, click Submit to submit the updated request.
   
   
   
   
5. The request will be routed directly to the domain approver that initiated the pushback. It does not need to be approved again by your Supervisor or Divisional approver (if applicable).
   
   
6. You can monitor the status of the Role ID included in the request on the My Roles landing page in the Pending Data Access Roles section.
   
   
7. You will receive an email notification once the request has been approved.

Denied Requests

If a request is denied, a new request will need to be created if the user wishes to re-submit.