Draft: Resolve "Create MR to instruct Support on how to handle residency document (COR) requests"
requested to merge 14401-create-mr-to-instruct-support-on-how-to-handle-residency-document-cor-requests into master
Why is this change being made?
We do not currently have any documentation detailing how to handle residency document (COR) requets. This MR will create a new handbook page updating our workflows and instructing Support on how to handle these requests.
Author Checklist
-
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.
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Closes #14401 (closed)
Edited by Greg Long