Addition of Customer Roundtables to "Enable" Section of CSM Handbook

Why is this change being made?

Customer roundtables have been added as a tool to further enable our customers. Roundtables are initially industry specific but can span industries where common interests are to be found (heavily regulated industries for example):

The roundtables encourage customers to share common (industry specific) challenges and their solutions with each other facilitated by a Customer Success Manager.

The aim is to strengthen the relationship with the customer, gain new insights into how GitLab is used to address customer challenges, and find areas of improvement.

Customers will be able to keep collaborating with each other in dedicated, private collaboration spaces after the event.

An event should be organised once a quarter as this helps foster strong, lasting relationships between participants.

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 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
• 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
  • 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
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---