Remove Duplicate Zoom Page

#### If you see something, say something

Shadows should notify GitLab meeting participants if their [name and job title](/handbook/tools-and-tips/zoom.md#adding-your-title-to-your-name) are not mentioned on Zoom.

Shadows should notify GitLab meeting participants if their [name and job title](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-additional-config/#customize-your-zoom-profile) are not mentioned on Zoom.

If a GitLab team member is sharing their screen before introductions have occurred, shadows should remind GitLab presenters that GitLab does not [recommend sharing screens during zoom meetings](/handbook/tools-and-tips/zoom/#sharing-your-screen-in-zoom) and to please wait until after introductions have been completed to allow participants to see each other clearly during introductions. This is especially important during external calls when participants are meeting each other for the first time.

If a GitLab team member is sharing their screen before introductions have occurred, shadows should remind GitLab presenters that GitLab does not [recommend sharing screens during zoom meetings](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-additional-config/#enable-screen-sharing) and to please wait until after introductions have been completed to allow participants to see each other clearly during introductions. This is especially important during external calls when participants are meeting each other for the first time.

If you notice that someone does not have their picture set in Google when a Google document is being actively worked on, [let them know how to set one](https://myaccount.google.com/personal-info) so their picture will show up in the document rather than their first initial. That makes it easier for everyone to find where they are in the document, especially when they are speaking. Let them know that this is 100% optional.

### CEO's Calendar

1. At the start of the week, review the CEO's calendar. The CEO's calendar is the single source of truth. Shadows should check the CEO's calendar for updates often. You will not be invited to each meeting. Meetings that the shadows may **not** attend will have a separate calendar entry on the CEO's schedule that states "No CEO Shadows". When in doubt, reach out to the CEO's EBA to confirm if you should attend or not. There will be some meetings and events the shadows do not attend. Do not feel obligated to attend every meeting — all meetings are considered optional.

1. As a reminder, you should have your title updated within your last name on zoom. During the Shadow rotation update your title to "CEO Shadow". [Here is the how to](/handbook/tools-and-tips/zoom/#adding-your-title-to-your-name) update your title as part of your last name to ensure it shows up on zoom.

1. As a reminder, you should have your title updated within your last name on zoom. During the Shadow rotation update your title to "CEO Shadow". [Here is the how to](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-additional-config/#customize-your-zoom-profile) update your title as part of your last name to ensure it shows up on zoom.

1. Add the CEO's calendar to your Google Calendar by clicking the `+` next to "Other Calendars". Then click `Subscribe to Calendar`, search for the CEO's name, and click enter.

1. Because candidate interviews are marked as "private" (busy) for confidentiality reasons, the EBA will invite the shadows to those events directly. As a result, you will get an email from Greenhouse asking for candidate feedback, which is not necessary.

1. Meetings with those outside of GitLab may not be on Zoom. Prior to the call, check the CEO's calendar and load any other conferencing programs that may be needed. It may be necessary to dial in via phone for audio-conferences. If you have any problems confirming the link, reach out to the EBA in the `#ceo-shadow` slack channel.

### Meetings are recorded

Remote meetings can be recorded, especially when key individuals aren't able to join live. This allows team members to catch up on what transpired, adding context to notes that were taken during the meeting. Learn more about recording in Zoom in the [Tips and Tricks section of GitLab's Handbook](/handbook/tools-and-tips/zoom/#recording-in-zoom).

Remote meetings can be recorded, especially when key individuals aren't able to join live. This allows team members to catch up on what transpired, adding context to notes that were taken during the meeting. Learn more about recording in Zoom in the [Tips and Tricks section of GitLab's Handbook](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-recording).

### Inclusive

#### Record meetings to encourage async participation

You should aim to record all meetings. This allows team members to catch up on what transpired and adds context to notes that were taken during the meeting. Learn more about recording in Zoom in the [Tips and Tricks section of GitLab's Handbook](/handbook/tools-and-tips/zoom/#recording-in-zoom).

You should aim to record all meetings. This allows team members to catch up on what transpired and adds context to notes that were taken during the meeting. Learn more about recording in Zoom in the [Tips and Tricks section of GitLab's Handbook](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-recording).

#### Managing meeting attendance for team members

1. When referencing a team member's name in the meeting agenda, ensure that both the first and last names are displayed. (e.g: When we write the name of the person who is speaking in the agenda, we should write the first and last name or use the tagging feature as a prefix)

1. For action items, we [go directly to a GitLab issue](/handbook/communication/#start-with-a-merge-request) or [merge request](https://docs.gitlab.com/ee/user/project/merge_requests/). This creates a direct takeaway from the meeting, where ideas are summarized and action can begin immediately. Be sure to add a link the issue or MR in your meeting agenda for reference and completeness.

1. For optional attendees, or key team members who could not attend the meeting live, tagging them in the resulting GitLab issue(s) enables them to get themselves up to speed and contribute when it is suitable for their schedule.

1. Record the meeting. You can always delete an unwanted meeting, but you cannot turn back the clock and record a meeting retroactively. This is particularly important if you want to present or wish to have a written transcription of the meeting. Zoom's [Cloud Recording](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064927) supports [transcription](/handbook/tools-and-tips/zoom#recording-video-transcripts) natively, and [Otter](https://otter.ai) is another popular transcription tool.

1. Record the meeting. You can always delete an unwanted meeting, but you cannot turn back the clock and record a meeting retroactively. This is particularly important if you want to present or wish to have a written transcription of the meeting. Zoom's [Cloud Recording](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064927) supports [transcription](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-recording/#recording-video-transcripts) natively, and [Otter](https://otter.ai) is another popular transcription tool.

### 6. Use the right tools

  - *Event name*: Name your event based on the length of time or specific topic/focus (Ex: New Customer: Onboarding Call)

  - *Location*: Custom (Use a Static Link from Chorus Scheduler generated from your Zoom PMI)

    - Next, add the go.chorus.ai link to your calendly event configuration Location field.

      - *Important Note*: Anyone booking through your calendly would use the same location link when booking an event instead of an automatically generated unique meeting ID per meeting. Please make sure your Zoom Personal Meeting follows GitLab's best practices on [privacy and security](/handbook/tools-and-tips/zoom/#a-note-on-privacy-and-security).

      - *Important Note*: Anyone booking through your calendly would use the same location link when booking an event instead of an automatically generated unique meeting ID per meeting. Please make sure your Zoom Personal Meeting follows GitLab's best practices on [privacy and security](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-security).

      - Make sure to select display location only after confirmation

      - ![calendly-location](/images/customer-success/csm/calendly/calendly-location-chorus-go.jpeg)

### Meeting Recordings and Summary

Zoom meetings can be [recorded](/handbook/tools-and-tips/zoom/#recording-in-zoom) or [summarized](/handbook/tools-and-tips/zoom/#zoom-ai-companion) using the AI Companion feature provided by Zoom. Meeting Summaries allow the people who could not attend a call to quickly catch up on discussions, decisions and action items. This makes it easier for everyone to stay informed and enhances productivity and efficiency. The feature is turned off by default and can be enabled by the meeting host. The meeting host should always ask all attendees if it is alright to record or summarize the call. Additionally, all attendees will see a notification banner when Zoom call recording or Zoom AI Companion get enabled. This is especially important for customer meetings. If the customer does not want Zoom call recording or Zoom AI Companion to be used, the host should turn it off. We also have a section about call recordings in our [Privacy Statement](https://about.gitlab.com/privacy/).

Zoom meetings can be [recorded](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-recording) or [summarized](/handbook/security/corporate/end-user-services/supported-apps/zoom/zoom-ai) using the AI Companion feature provided by Zoom. Meeting Summaries allow the people who could not attend a call to quickly catch up on discussions, decisions and action items. This makes it easier for everyone to stay informed and enhances productivity and efficiency. The feature is turned off by default and can be enabled by the meeting host. The meeting host should always ask all attendees if it is alright to record or summarize the call. Additionally, all attendees will see a notification banner when Zoom call recording or Zoom AI Companion get enabled. This is especially important for customer meetings. If the customer does not want Zoom call recording or Zoom AI Companion to be used, the host should turn it off. We also have a section about call recordings in our [Privacy Statement](https://about.gitlab.com/privacy/).

## Slack Channels