Badger Data Access: Pushed Back and Denied Requests

This document provides an overview for users on how to address requests that have been pushed back or denied by an approver in the Badger Data Access application.

 Approvers may approve, deny, or push back an access request for changes or clarification.

Pushed Back Requests

If a request is pushed back by a Supervisor or Divisional approver, the user must make any necessary adjustments to classification, row level, and justification and re-submit. After re-submitting, the request must pass all required approvals again, beginning with the Supervisor.

If a request is pushed back by a Domain Steward, the user must make any necessary adjustments to classification, row level, and justification and re-submit. After re-submitting, the request is routed directly back to the Domain Steward, skipping the Supervisor and Divisional approver (if applicable) steps as they have already made their approval for the given domain.

Note: Only roles included in the original request may be adjusted or deleted. For additional roles, submit a new request for access.

Requests Pushed Back by Supervisor or Divisional Approver

  1. When an approver pushes back a request, the user will receive an email notification that it was pushed back and requires clarification.

    Image of notification to user when request is pushed back

  2. Click the link provided in the email to access the pushed back request.

    1. Requests that have been pushed back 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.

      Image of pushback container in application

  3. Review the Reason for Pushback and make adjustments as necessary

    1. Click the Pencil button to edit the Classification and/or Row Level Security for a corresponding Domain/Subdomain.

      Image of reason for pushback and pencil icon to modify

    2. If the request includes multiple domains and you need to remove one, use the trashcan icon on the corresponding row to delete it.

      Image of trashcan icon to remove role from a pushedback request

    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.

      Image of Delete Entire Request button

  4. Adjust the Classification Level and Row Level Security as needed.

    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.

    Image of Edit a Role popup

  5. Append to the Justification as necessary and click Submit.

    Image of appended justification and submit button

  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.

    Image of pending data access roles

  8. You will receive an email notification when the request has passed all required approvals.

Requests Pushed Back by Domain Steward

  1. When an approver pushes back a request, the user will receive an email notification that it was pushed back and requires clarification.

    Image of notification to user when a request is pushed back by a domain steward

  2. Click the link provided in the email to access the pushed back request.

    1. Requests that have been pushed back by a Domain Steward 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.

      Image of Domain Steward Pushbacks section on user landing page

  3. Review the Reason for Pushback and make adjustments as necessary

    1. Click the Pencil button to edit the Classification and/or Row Level Security

      Image of pencil icon to make edits to classification or row level and reason for pushback entered by steward

    2. Make adjustments to Classification and/or row level

      Image of popup to edit classification or row level security

    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.

      Image of trashcan icon to delete role and terminate request

  4. Use the Comments box to send a comment back to the Domain Steward or to elaborate on the original Justification for access, as requested by the Steward. Then click Submit to submit the updated request.

    Image of Comments field and Submit button

  5. The request will be routed directly back to the Domain Steward that pushed it back. It does not need to be approved again by your Supervisor or Divisional approver (if applicable).

  6. You can monitor the status of theRole 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.


Keywords:
badger data access, pushback, push back, push, deny, denied, modify, resubmit, delete, data, warehouse, access, security 
Doc ID:
153036
Owned by:
Wendy G. in Data KB
Created:
2025-07-07
Updated:
2026-03-04
Sites:
Data, Academic Planning & Institutional Research