The host account hides the participant's first ten minutes
When a facilitator rehearses from their own logins, every door opens. The host is never in the waiting room, the server owner never meets a verification requirement, and the Drive owner sees the handout whether or not the link works for anyone else. The rehearsal passes, and the first real participant still gets stuck.
A useful rehearsal walks the participant's path with the participant's kind of account. The decision is which tools need a separate rehearsal login and which can be tested without one.
Zoom: who lands in the waiting room
Zoom's waiting room lets the host control when each participant enters. Its options can send everyone to the waiting room, or only participants who are not on your Zoom account or not signed in, and choosing these options and customizing the waiting room requires a paid account.
That rule decides the rehearsal. A colleague who signs in with a login on the host's own Zoom account may skip the waiting room entirely under the second option, while real participants will not. Rehearse with a Zoom login that sits outside the host's account, or join signed out, so the waiting-room message, the admission step and the first view of the room match what participants will see.
Discord: verification levels and the phone exception
Discord servers set a verification level. At High, a member needs a verified email, a Discord registration older than five minutes and more than ten minutes in the server before sending text messages; at Highest a verified phone is also required. Users who do not meet the level cannot send text messages or join voice channels.
One detail changes how you rehearse: Discord says a verified phone number on an account supersedes all the other requirements. If your rehearsal account has a verified phone, it will never see the wait that a newly registered participant with only an email meets. Use a rehearsal account with only a verified email to experience the real first minutes, and write the welcome channel for that person.
Drive: test signed out before buying anything
Handouts need no extra account for rehearsal. Google's help says a file shared with anyone with the link can be used without signing in to a Google Account, and visitors who are not signed in show up as anonymous animals. Open the link in a private browser window that is signed out; if the file opens there, it will open for participants with the same link.
A separate Google login is only worth having in the rehearsal if part of the workshop deliberately requires sign-in, such as a form with a file-upload question.
A dry run, worked through
Hypothetical: a facilitator preparing a first community workshop asks a producer to play the participant. The meeting admits only signed-in Zoom users, so a signed-out join cannot stand in for a participant; the producer joins Zoom from a login on a different account and sees the waiting room with its default message; the team rewrites the message to name the start time and what to have ready. In Discord, the producer uses an account with only an email verified and meets the High-level wait; the team adds a short rules channel that new members can read during those minutes.
The handout link opens in a signed-out window, so no Google login is needed for that check. Two rehearsal logins were needed, not three, and the changes the team made would never have surfaced from the host's chair.
The team keeps the dry run as a short script: join, wait, enter, open the handout, post a first message. At each step the producer notes what the participant actually sees. They repeat the script after any settings change, because a new verification level or waiting-room option alters the participant's path without changing anything on the host's screen.
Which rehearsal logins to buy, and which to skip
Buy a participant-side login only where the participant's view depends on account state: Zoom when the meeting requires participants to sign in, so a signed-out join cannot reach the waiting room, and Discord when the server uses a verification level. Skip it where a signed-out browser shows the same thing, as with link-shared Drive files or a Zoom meeting that admits signed-out guests to the waiting room.
Keep rehearsal accounts with the producer who runs the dry runs. Discord's terms rule out lending or transferring accounts, and Zoom's terms do not allow an account to be shared with another individual, so the rehearsal login is one person's tool, used for every rehearsal that person runs.
Comparing rehearsal accounts on rStock
rStock is independent of Zoom, Discord and Google, and no listing on it carries their endorsement. For a Discord rehearsal account, the details that matter are whether a phone is verified, since that changes what the account will see, and whether the email can be moved to your control. For a Zoom rehearsal login, the useful detail is simply that it is a standalone account outside your host account.
Pay from your rStock balance, open the delivery record on your order page and run the first dry run while the window shown there is still open, so a login that does not match its description can be raised in time. Then compare listings for the rehearsal logins your plan actually needs.