Skip to content
All guides

Business tools

Split Host, Producer and Channel Admin Roles in Zoom, Telegram and Drive

Facilitation teams often share one login to save time. Assign each person a role in Zoom, in the Telegram announcements channel and in Google Drive, and the account purchase becomes a short, specific list.

Contents

Three jobs, three tools, one shared password

Many small facilitation teams start the same way: the lead facilitator's Zoom login, Telegram account and Google Drive run everything, and the producer signs in with that password when needed. It works until two people need to act at once, the facilitator is ill, or the password changes the night before a session.

The better structure gives each person their own login and a defined role in each tool. Doing that well means knowing what each role can and cannot do, because the three tools draw their lines in different places.

Write the jobs down before assigning anything. The facilitator teaches and makes decisions in the room. The producer opens the session, admits people, runs breakout rooms and posts reminders. Someone keeps the announcements channel current, often the producer again. Each job maps to a role in one tool, and only some of those roles need an account of their own.

What a Zoom co-host can and cannot do

Zoom's co-host shares most of the host's in-meeting controls, such as managing participants, but cannot start a meeting. The host has to promote a participant to co-host during the meeting; co-hosts cannot be assigned ahead of time, and only the host can end the meeting or promote others.

If the producer must be able to open the session when the facilitator is late, Zoom's answer is an alternative host, and that comes with a condition: both users must be licensed with a paid license and on the same Zoom account. A producer with a separate standalone login cannot be the alternative host for the facilitator's meetings, however capable the login is.

Telegram admin rights for the announcements channel

Telegram lets a channel owner add administrators and set rights for each one individually. A producer who posts reminders and links does not need the right to add other admins or remove subscribers. Telegram also offers admin signatures; if they are disabled, subscribers cannot tell whether the owner or an administrator posted, which matters when the producer writes on the facilitator's behalf.

Each admin is a separate Telegram account tied to that person's own mobile number, which is exactly why the producer should use their own account rather than borrowing the facilitator's.

Drive ownership for workshop materials

In Google Drive, ownership is the role that survives people leaving. Google's help explains that ownership can only be transferred to someone the file was already shared with, that a personal account cannot transfer to a work or school account, and that after a personal-account transfer the previous owner becomes an editor once the new owner accepts.

That makes a dedicated workshop Google account the cleanest owner for slide decks, handouts and forms: the facilitator and producer work as editors, and nobody has to transfer files when the team changes.

A two-person team, role by role

Hypothetical: facilitator Lena and producer Omar run a monthly six-week course. Lena hosts on a paid Zoom account, and the team adds a second licensed user on that same account for Omar so he can be the alternative host. In each session Lena also promotes Omar to co-host so he can manage breakout rooms. In Telegram, Omar has his own account with rights to post and edit messages in the announcements channel, and signatures are switched on. In Drive, a workshop Google account owns the course folder, with both of them as editors.

Their purchase list is short: one extra licensed Zoom user on the existing account and one workshop Google account. Omar's Telegram account is his own. Nothing is shared by password, and when Omar moves on, his roles are removed without touching anyone else's login.

Fit and not-fit for a separate account

A separate account fits when a role needs its own identity: a second licensed Zoom user on the same account, a Google account that owns materials independently of any one person, or a Telegram account for a team member who should not use a personal number with participants.

It does not fit when the need is only a role inside an existing setup, such as co-host or channel editor. In that case the person's own login, given the right role, already covers it, and an extra account only adds a password to look after.

Buying the accounts the role map calls for

rStock is an independent marketplace and has no affiliation with Zoom, Telegram or Google. When a Zoom listing is involved, note whether it is a standalone account or a seat in another organization, because an alternative-host arrangement needs both users on one account: a separately bought login cannot become the alternative host on an existing team account, but a standalone paid account can serve as the team's host account, with the producer's licensed user added there through Zoom. Zoom's terms treat host rights as personal to one user and limit transfers to cases Zoom approves in writing; Telegram's FAQ says an account can only be connected to a mobile number, which is how Telegram identifies its user; Google holds each person responsible for what they do with their account. Follow each brand's terms with the account you choose.

rStock has no pre-purchase messaging with stores, so if a listing leaves the account type unclear, pick one that states it. Payment comes from your rStock balance, the account is delivered as a record on your order page, and the payment is held for the window shown there while you check the login. Compare the Zoom, Telegram and Google accounts that your role map actually calls for.

Frequently asked questions: Split Host, Producer and Channel Admin Roles in Zoom, Telegram and Drive

Keep reading