Partner Sourced DR Process Overhaul - Formatting Changes
Why is this change being made?
We are redesigning the Partner Sourced Deal Registration process to:
- drive tighter collaboration with field and partner sales
- ensure Partner Sourced DRs are appropriately reviewed/approved by the field as part of the approval process
- tighten up compliance around the Registration object by removing edit rights on all fields for non-operations users to ensure any necessary changes are appropriately reviewed/approved/documented.
These changes go-live in the system on May 8. The main MR to update our process documentation in the handbook for the new process and an additional MR for formatting/other minor adjustments were already merged. This MR is to adjust formatting and make final changes/adjustments.
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, and the content is SAFE
-
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
- The when to get approval handbook section explains the workflow in more detail
- 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.
Edited by Nick Scala