Gitlab hero border pattern left svg Gitlab hero border pattern right svg


On this page

Post everything

We post everything that doesn't contain confidential information to YouTube. We found that it helps with:

  1. Hiring because candidates can get a feel for the company by seeing meetings.
  2. Retention because sharing reinforces our value of transparency.
  3. Community because people feel more part of what is happening at the company.
  4. Sales because people see our training materials they sell themselves.
  5. Enablement because people can find detailed content about certain subjects.
  6. Awareness because lots of time is spent on YouTube and our videos get lots of views in aggregate.
  7. Training because content on YouTube is easier to consume even for team members, see why not Google Drive

No quality bar

You don't need to be worried that something is not of the high enough quality because:

  1. You can use the GitLab Unfiltered YouTube account if the conversation is intended for team members only.
  2. Algorithms will ensure that a video will be distributed to the right sized audience.
  3. We can embed videos if and where they are relevant, for example in docs.
  4. Enhance videos later if we need to (trim it so it starts immediately, add transcript, extensive description, links to relevant materials)
  5. Follow up later if we need to (rerecord, do an interview)

No extra work

Producing videos shouldn't be extra work. You should do what you normally do. But when a meeting is possibly interesting for more people, make it a livestream. Or when you start talking about something possibly relevant to more people, hit the record button.

Make private quickly

In case there are any concerns raised about a video everyone has the authority to make it private. You don't have to wait for any permission, just go to the channel specific YouTube Studio, for example the one for unfiltered and mark the video private. Please note that there is another tab for live videos. In case you marked it private while it doesn't need to be it will be easy to undo it by marking the video public.

Why not Google Drive

Always use YouTube and never use Google Drive, even for private videos, because YouTube videos:

  1. are streamed more reliably.
  2. have mouse-over thumbnails.
  3. can be played at a higher speed.
  4. can be fast forwarded and rewound in 10-second blocks.
  5. can be timeshifted by adding them to a watch later list.
  6. can be embedded, for example in the handbook.
  7. restart at the right spot after being reloaded.
  8. can be easily viewed on other devices, like TVs or streaming devices, with YouTube support.
  9. allow links to a specific time in the video.
  10. can have subtitles added automatically.
  11. are zero rated by some mobile providers
  12. will be served to people when it is relevant, automatically, since YouTube is a distribution channel.
  13. allows anyone to contribute by leaving comments.
  14. public videos show up in Google search.
  15. easy to make public if the video is suitable for that.
  16. they have playlists that you can use to organize them.


There are two YouTube channels we use at GitLab:

  1. Main: used for content intended for people in the wider community, for example a conversation between two teammembers about multi-cloud.
  2. Unfiltered: used for content intended for teammembers, for example a weekly meeting of the Plan group.


There are three types of visibility:

  1. Main
  2. Public
  3. Private

The level of visibility should be displayed clearly in the titles of calendar invites. For example when you do a livesteam to the public channel say: "Private stream" at the start of the invite. You can skip live in livestream since every stream is live. Do not say Unfiltered stream since it is ambiguous. Do not say just livestream since people don't know what the level of access is.

We don't post:

  1. Unlisted videos on any channel, this is too insecure for sensitive materials and not findable enough for public materials.
  2. Private videos on our main channel, all videos here are for a wider audience.
  3. Use Google Drive for any video, since it has many drawbacks.


  1. GitLab Filtered: To request access follow the instructions secret note 'YouTube Access' in the team vault in 1password.
  2. GitLab Unfiltered: Everyone should get access to YouTube unfiltered during onboarding. If you do not see an invitation in your Inbox, please check the Pending Invitations section of your GSuite account.


Remember that when you're signed into YouTube using an official GitLab account that any interaction you may have with other groups or people on the site (e.g. such as in the comments sections of videos) will be perceived as official communication from the company. In almost all cases, unless your job specifically requires you to interact in a community manager role or capacity, it is best to switch to a personal account prior to engaging with a video or user on YouTube.


Our YouTube channels contain a lot of content. As a result it can often be hard to find videos once they are published. Make liberal use of tags and playlists to organize video content you publish. For published recordings of recurring meetings, create a YouTube playlist.

Upload conversations to YouTube

  1. If you have a conversation that might be interesting please hit "record" (unless the meeting is being livestreamed already). Unless stated or arranged otherwise, our expected behavior is that the meeting organizer is responsible for distributing the recorded content after the meeting.
  2. Log in to the Zoom account of the meeting and go to the menu on the right and choose "My Recordings" (it can take up to 30 minutes before the recording is available to be shared).
  3. Select the meeting and download the recording to your computer (if you can't find the recording because it was a while ago check "Trash" in the menu on the top left and "Recover" the recording).
  4. Go to the YouTube upload page and log into the channel. If you're logged into your personal YouTube account, you may need to first log into your GitLab YouTube account to access the channel. If you're already logged into your GitLab YouTube account and have access to the channel, you need to switch accounts to that channel. To switch accounts, click on the account icon in the top right corner and then click "Switch account".
  5. Drag and drop your recording into the window to upload it. Keep the privacy dropdown on the default 'Public' setting (unless there is confidential material). Use the dropdown menu to set the video to private if it the video contains confidential material.
  6. While it's uploading, edit the title and description. Place "Confidential:" at the beginning of the video's title if the video will be kept private on our YouTube channel.
  7. Be sure to include relevant links (for example a handbook page or presentation) in the description, and add the video to any relevant playlists.
  8. When it is done uploading, press publish, then click on the Embed tab and copy the code, and insert that in the relevant part of the handbook or documentation.
  9. After uploading a video to the GitLab Filtered channel, be sure to add a link to the new video in the #content-updates channel in Slack.

Don't worry about the quality

  1. There is no minimum quality, so please share it on our GitLab YouTube channel, as long as there is nothing inappropriate or confidential.
  2. Everyone at the company probably has at least one conversation every week that is relevant to more people, so please share it.
  3. We always list videos publicly instead of having them unlisted, unless there is confidential material. This allows more people to find the content. If the material is confidential, set the video to private.
  4. Don't worry about whether or not it will be interesting to absolutely everyone. Just give it a descriptive title so people know what it is about, and let them decide whether or not they should watch it.
  5. Make sure that all participants are aware that you're recording.
  6. You don't have to be sure it is interesting and OK to share when you start recording; you can make that decision after the fact.
  7. If you record an in-person conversation with your mobile phone please hold your phone in landscape (horizontal) mode.

Cam streaming

Talking is faster than typing and allows you to add non-verbal clues. YouTube allows you to stream with a webcam. Go to /webcam and make sure you're logged into the right account (YouTube Unfiltered). Your stream will be public by default.

Live Streaming

Why livestream?

We prefer livestreaming over recording and uploading because:

  1. Allows more people to participate in real-time.
  2. You don't have to upload the video to YouTube later on.
  3. You can't forget about uploading the video.
  4. It is clear to all participants that the content will be public.

But it can happen that you're not in a livestream and something interesting comes by. In that case you can record and upload.

Considerations for live streams

  1. Please remember to start live streams exactly at start time to avoid dead space at the beginning of the call.
  2. If you're not a host, you can't live stream direct from zoom so, the host will need to do that.
  3. Generally, for a live stream, it's helpful to have a separate person handling promoting people to panelist.

Livestream with Hangouts

  1. Notify participants the meeting is being livestreamed before, and at the start of, the meeting.
  2. Check the GitLab Team Meetings calendar to see if any other livestreams are scheduled at the same time. There can only be one livestream per YouTube channel. In the case that you start a livestream while one is already occurring, you will override the first livestream and merge your stream into their video.
  3. Login to the GitLab YouTube account or the GitLab Unfiltered YouTube account. (Read the secure note in 1Password called "YouTube" for instructions on how to get access).
  4. Click on the Tanuki in the upper right corner. Choose "Creator Studio"
  5. Choose "Live Streaming", then "Events" from the left side menu, and click on "New live event" in the upper right corner.
  6. Give your event a title, description, and keep the privacy dropdown on the default Public setting.
  7. Set the time of the livestream, and set the "Type" to 'Quick'. If you want to go live immediately, keep the default Now setting and choose "Go live now". This will place you in a Google Hangout but will not automatically begin the livestream.
  8. To schedule the live event for later, choose the day and time from the drop downs, and click "Create event" to save.
  9. To start your scheduled live stream event, navigate to the "Events" page in YouTube, find your event, and choose "Start Hangout On Air". This will place you in a Google Hangout but will not automatically begin the livestream.
  10. Up to 50 participants can join the Google Hangout. To invite participants, click on the Invite People icon from menu in the top center of screen. You can either share the permanent link, or invite individuals.
  11. Once capacity is met, anyone else can participate via the YouTube Watch page.
  12. When you are ready to broadcast, choose the green "Start Broadcast button" at the bottom of the Google Hangout console. You will see a "LIVE" message once streaming.

Livestream with Zoom

  1. Configure your Zoom advanced meeting options to enable livestreaming for youtube

click the more button

  1. Verify that there are no other livestreams happening at the same time as yours, and add the livestream to the GitLab Team Meeting calendar.

  2. Click the [ More ] button and click Live on YouTube

click the more button

  1. Select the GitLab Unfiltered or GitLab

choose your account

  1. Grant permissions to the GitLab account by clicking the [Allow] button

grant permissions

  1. Tell the person who will do an intro 'Going live, be ready to kick it off' and then click Go Live!

configure stream

  1. A person does an into where they state who they are, what their role is, and what the meeting is about.

Advanced setups

Depending on your needs, you might want use software to provide overlays and/or reroute audio. 99% of the people at GitLab don't use this, but see below for instructions if you do want to use it.


Audio Rerouting


obs studio preferences

When to record and publish to YouTube