I haven't tried to gdoc-ize any of this yet, I think better in text.  It's
more in the class of "Hybrid PREP manual" rather than "operations"...

 =====

Zoom setup/pre-execution

Buy as many licenses as needed, which turns on "pro" status
  make sure payment-method isn't going to go sour once charges appear
  license per "track" + social, unless back-to-back session layout
  Also buy sufficient recording cloud-storage if needed

Need a handful of working email addresses / aliases in a domain
  a G-suite under a domain is convenient
    or any other controllable mailserver setup
    Member/Admin users do NOT need to be in the same domain!
  Make Zoom-user addrs point to a common distrib list
    then fan that out to account-admins, so everybody sees all email
  Under master Zoom login, "add user" to invite each sub-user address in
  Answer the links to join users to the infrastructure & create logins
    keep password structure simple, except for admin-level users
  Temporarily admin users cannot detach their accounts until non-admin

Group all the intended "runtime" users
  Manage settings via the group, "lock" the critical stuff
    locking helps force the settings to genuinely propagate, I think
  Make sure to set:
    Co-hosts
    Group HD video
  Either account-admin or separate group-admin can handle most of that

Assign licenses and optionally, webinar add-ons
  Move each session-runner user from "basic" to "licensed"
  Add webinar if relevant
  Each user can run one session at a time, e.g. a "track" or "half-track"
  Admin users [incl. master account!] don't need licenses, unless they
    will need to run sessions too  [or talk to Zoom support, grrr]

Try to kill forced 2FA across master account:
  go to "advanced -> security" and down a ways, "one-time passcode auth"
  likely defaults to ON, turn it OFF, esp. if sharing user accounts

Log into each user under incognito, handle "2fa" via emailed code if needed
  Admin can manage users individually via Zoom portal login, but an actual
    fresh user login from someplace often triggers "check for a code"
  Remember that in portal, left-sidebar upper profile/settings/meetings etc
    is only for that one user that's logged in!
    sub-user config is accessed from the "users" list, or groups

Where should run-times log in and start sessions from, and by who?
  remote or in-room tech option : have to divulge runtime passwords
    Be prepared to handle further unexpected 2FA on-site and provide codes
    Hopefully "new" login locations or "new" machines won't trigger it
  NOC-host option with co-hosting from there : needs coordination/joining
  NOC monitor-only option
    If 3rd-party streaming, in-room stream source MUST be logged into the user
    NOC can still have special joinlinks for monitoring
    NOC boxes shouldn't be logged into Zoom at all, just join

Tech comms backend
  group text  [Discord, keybase, some other near-realtime chat]
  voice/video channel on separate device [potential brain overload / babble]

Plan how event tracks run
  meeting, webinar, or other streaming?
  depends somewhat on desired level of attendee interactivity
  chat etc can be on alternate platform, if people are willing to flip apps
  Recurring meetings can start & stop at will, incl. practice runs
  Recurring/anytime cannot have Zoom-based registration

Set up sessions
  Single meeting/webinar, or separate, at what granularity?
    We've been commonly doing per-track per-day
  Single over whole event has more risk from "bombing"
    but any info leak can bring that on regardless
  One-way streaming mitigates risk, albeit more "isolating" for viewers
  Webinars: "practice session" for panelist setup at beginning or not?
  Generate stream-keys for external service if needed
    Are streamkeys reusable or one-shot?  service-dependent
  Generate access links for panelists/participants, attendees/viewers
    Webinar special "panelist" links CAN be generic and shared
  Add links to event database, whatever that consists of
    Send join info and checklists to panelists, in whatever form
  Timed session "release", or whole schedule's worth visible to attendees?

Recording settings
  [this can spawn its share of debates]
  Decide on per-session segments or one all-day monster per track