# 🚀 Onboarding for Leads
Welcome to UBC Launch Pad, and congratulations (and thank you!) for joining us as a lead!
# Checklist
# Slack Channels
Everyone should join a private channel named #tm-leads-YYYY (for example, #tm-leads-2020). If this channel doesn't exist yet, coordinate to get it created. This will be the primary means through which Launch Pad leadership works together. In addition, make sure you join:
#ask-leads: this is where members are expected to direct questions at leadership.#ask-rocket: our Slack bot Rocket is how teams are set up and managed - make sure you familiarize yourself with the app and ask this channel if you have questions or something is broken.#ask-design: questions for design#ask-strategy: questions for strategy
As a lead, you should also lead in Slack participation by example - please make sure you join any channels you find interesting and participate in them! See our Slack guide for more details.
# GitHub Teams
Make sure you are a part of:
@ubclaunchpad/leads, and check that you can access the Leads repository@ubclaunchpad/strategy, and check that you can access the Strategy repository@ubclaunchpad/design, and check that you can access the Design repository
Additional, the president(s) should also be a part of @ubclaunchpad/exec and familiarize themselves with the Exec repository, where we keep track of accounts and credentials.
TIP
Make sure that you are watching all relevant repositories so that you don't miss any updates! To learn more about setting up your GitHub notifcations, check our GitHub guide.
# Google Drive
Make sure all leads are given "editor" access to the shared Launch Pad folder, which is owned by the team@ubclaunchpad.com account (more details are in the Exec repository).
TODO: detailed drive hierarchy
# Workflows
TODO: how leads will use handbook / GitHub / Drive etc.