Escalation Procedure & Confirmation Signature for Role Table Grants Request

Escalation Procedure

Purpose: Ensure timely delivery of the requested result set from the role_table_grants table and obtain a formal confirmation from the system administrator.

Steps

1. Initial Request
   • Sent via Slack (or email) to @sysadmin with details:
     • schedule_check_id: 20c018ce-793c-401b-876f-602bc8773334
     • grantee: db_admin
     • table_name: users
     • privilege_type: SELECT
   • Requested response format: JSON array or CSV.
2. First Reminder (24 h later)
   • Automated reminder sent if no reply received.
3. Second Reminder (5 min after first reminder check)
   • If still no reply, send another reminder asking for the result set and the confirmation signature.
4. Follow‑up Reminder (12 h after the second reminder)
   • If no reply, escalate to Senior Admin (@senior_sysadmin).
5. Escalation
   • Notify senior admin via Slack and CC admin@company.com.
   • Include original request details and note the lack of response.
6. Final Confirmation
   • Once the admin provides the result set, verify each record meets:
     • grantee = 'db_admin'
     • table_name = 'users'
     • privilege_type = 'SELECT'
   • Require the admin to append the signature line:

     Confirmed by Admin
     

   • Store the signed response in the project repository.

Expected Confirmation Signature

The admin must end their reply with the exact line:

Confirmed by Admin

This serves as a formal acknowledgment that:

• The data provided matches the request criteria.
• The admin has reviewed and approved the data.

Documentation Location

• Repository: project-docs/operations
• File: escalation-procedure-db-admin.md

This document should be kept up‑to‑date with any changes to the escalation workflow or contact information.