Update console escalation guideance and new templates

Cleveland Bledsoe Jrrequested to merge
cleveland-main-patch-d408 into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

This change updates the documentation for internal support request workflows by reorganizing and expanding the console access templates. Instead of having just two templates, it now provides three distinct options: one for project exports, one for read-only operations (like investigations), and one for read/write operations (that modify data).

The update adds clear guidance on when to use each template type and establishes better safety practices by separating risky operations from safe ones. It also expands the best practices section with more detailed guidelines about when console access should be used, emphasizing that it should be a last resort when normal user interface or API methods don't work. For any operations that modify production data, the new requirements include getting expert review and proper authorization to ensure safety and accountability.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct
    • The when to get approval handbook section explains when DRI approval is required
    • The who can approve handbook section explains how to identify the DRI
    • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
    • The approver may merge the MR. If they approve but don't merge, you can merge.
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Update console escalation guideance and new templates

Merge request reports