Voice Channels¶

Star Org Labs manages two kinds of voice channel, and they behave differently on purpose.

Join-to-create channels (voice hubs)¶

A hub is a voice channel that makes channels. Join ➕ Create Squad and the bot spawns a fresh channel shaped by that hub's template, moves you into it, hands you the controls, and deletes it once the last person leaves.

These belong to you, not to an op. Use them for the pickup group at 2am that nobody scheduled.

As the owner of a spawned channel you can mute, deafen and move people — but only in your own channel: the bot grants those as a permission on that channel, not across the server. One Discord quirk to know: a server mute or deafen stays on the member after they leave your channel, until a moderator lifts it. Unmute people before they head elsewhere.

How you change the channel itself depends on your server:

Servers in the control panel beta (below) give you a control panel in the channel's chat, the /voice commands and a web page. Discord's own channel settings are not open to you there, so every change is checked, rate-limited and logged in one place.
Every other server lets you edit your channel in Discord's own settings (rename, limit, lock and so on). Renaming has a short cooldown: Discord rate-limits channel renames, and a spammed rename would leave the channel stuck with the wrong name for everyone.

The control panel (beta)¶

On servers in the beta, the bot posts a control panel in your channel's text chat as soon as it moves you in. Every answer it gives is visible only to you. A button the server turned off for this hub isn't shown; a button the bot lacks a Discord permission for is greyed out with the reason ("Needs Manage Roles in Squads") — ask an admin to fix it.

Button	What it does
✏️ Rename	Opens a form. Discord allows two renames per ten minutes; the panel shows how many you have left and when the next one frees up. Mentions, formatting and invisible characters are stripped.
👥 Limit	How many people can join (0 = no limit). A hub may cap it.
🔒 Lock / 👁️ Hide	Lock stops new people joining; Hide hides the channel from people who aren't in it. Pressing again puts back what the category allows.
💬 Lock chat	Stops messages in the channel's chat (you and the bot can still post).
✅ Permit · ⭐ Trust · ⛔ Block	Pick a member. Permit lets them in this time; Trust lets them into your channels from now on; Block keeps them out and disconnects them. Pressing again on the same member takes it back.
👢 Kick	Disconnects someone in your channel.
🔁 Transfer	Hands the channel to someone in it. A short line in the chat names the new owner (no ping).
🙋 Claim	For everyone else: once the owner has left, anyone still in the channel can take it over. Not again for a minute after a hand-over.
🚪 Waiting room	Opens a waiting channel next to yours — see "Waiting room" below.
🔗 Invite	A one-hour invite, shown only to you — see "Sharing an invite" below.
📝 Status	The channel's status text; blank clears it. Once every 30 seconds.
🎚️ Region / bitrate	Voice region (or Automatic) and audio quality — only the qualities your server's boost level allows.
🔊 Sounds	Soundboard and external sounds on or off for everyone else.
♻️ Reset	Back to the hub's own settings (asks first). Your blocked and trusted people are kept; one-off permits and the invite are cleared.
💾 Save as my defaults	Keeps this setup for your next channels: For this hub or Everywhere (every org). The hub's rules always win, and a saved setting can only make a channel stricter.
🗑️ Delete	Deletes the channel (asks first).

You can't kick, block or hand the channel to someone ranked above you, to server staff (unless you're staff), to a bot or to the server owner. Right-click a member → Apps → Voice Kick, Voice Trust, Voice Block or Voice Transfer does the same as the buttons. Server staff (Manage Channels, or an org officer) can use any channel's panel, and those actions are logged as staff actions.

Typing your controls: /voice (beta)

Everything on the control panel is also a slash command, and every answer is private to you:

/voice rename, /voice limit, /voice status, /voice region, /voice bitrate
/voice lock, /voice hide, /voice chat-lock, /voice soundboard: pick On or Off, or leave it empty to flip it
/voice invite, /voice reset, /voice delete (reset and delete ask you to confirm)
/voice user permit, block, kick, trust or transfer with a member
/voice claim takes over the channel you're in once its owner has left
/voice defaults save keeps your channel's setup for next time
/voice waiting-room turns your waiting room on or off (pick On or Off, or leave it empty to flip it)
/voice knock with a member asks to join their locked channel

The commands work on the channel you're in, or on the one you own if you're not in voice. They follow the same rules as the panel buttons. If a server has turned a control off for a hub, the command is turned off too.

Sharing an invite

🔗 Invite on the panel (or /voice invite) gives you a one-hour invite to your channel. The link is shown only to you, in a reply nobody else sees, and on your My Voice Channel page. The panel everyone can read just says the invite is active, when it expires and who made it, so people who aren't allowed to invite can't copy it from there. Server staff can see the link on the live channel list. Locking the channel or deleting it kills the invite.

Leave the hub and come straight back and you're moved into the channel you still own. Once that channel is gone, a new one is ready after 30 seconds — join-and-leave churn would otherwise make and delete a channel every time.

My Voice Channel on the website (beta)

Where your org has turned on the new voice channel controls, My Voice Channel shows every channel you own right now, in any org, with the same controls as the panel in Discord: rename, user limit, lock, hide, lock the chat, status, region and audio quality, soundboard, an invite, permit, trust, block, kick, transfer, reset to the hub's defaults and delete. While you own a channel, the sidebar shows a small In voice: your channel chip under the Personal section that opens it, and your Member Homepage shows a small card with Lock, Hide and Limit. When you don't own one, neither appears.

The same rules apply as in Discord — two renames per ten minutes, nobody ranked above you can be kicked or blocked, and a control your org switched off isn't shown. Deleting from the website closes the channel within a few seconds. If the bot is missing a permission a control needs, the button is greyed out with the reason; if Discord refuses a control, wait a minute before trying it again (ask an admin to fix the bot's permissions).

The page is also where you edit your saved defaults: settings for every org, plus optional tweaks for one hub ("my Squad channels use limit 5"). The hub's own rules always win, and a saved setting can only make a channel stricter, never looser. Your defaults are private — an org can't see them.

Each channel card also carries the waiting room switch and the queue of people asking to join (when the hub offers the waiting room and the bot can run it), and Past channels lists the saved threads you're allowed to read. The page refreshes every 10 seconds while you're looking at it, and pauses while the tab is in the background.

Setting them up

Officers and admins configure hubs and their templates on the Voice Hubs page under Command Staff in the sidebar (orgs on advanced permissions can open it to a rank with the Voice Hub Management toggle). One template can back several hubs, so you describe the shape once — "Squad Channel" — and attach it to ➕ Create Squad and ➕ Create Wing alike, instead of maintaining two copies that slowly drift apart.

Editing a hub also lets officers choose which control-panel buttons its channels show and which roles may press them (with an optional cap on the user limit owners can set), a fallback category for when the hub's category is full, the thread and transcript options below, and a permission check that lists anything the bot is missing, with a "Re-check now" button. Server admins can also pick a voice role that members hold while they're in one of the hub's channels.

The same page lists every live channel — who owns it, how many are in it, and whether it's locked, hidden or has a waiting room, plus its live invite link, when that expires and who made it. Server admins can force delete a channel in an emergency; that skips the transcript. Saved transcripts are listed there too.

Getting the beta. The control panel is switched on per server by the Star Org Labs team while it's in beta. Until then, /voice answers "Not enabled on this server." and owners edit their channel in Discord's own settings.

Time spent in a hub channel does not count as event attendance. That's deliberate: hanging around in a party channel isn't the same as showing up for the op.

Threads and transcripts (beta, opt-in per hub)

A hub can be set to open a text thread for each channel it spawns, in a text channel the officers pick. Everyone who joins the voice channel is added to the thread, and it is archived when the channel closes.

If the hub also keeps transcripts, the thread's messages are saved when the channel closes and deleted automatically after the number of days the hub sets (1 to 90). The thread's first message and the channel's control panel both say so, and for how long. Only the thread is saved — voice is never recorded, and the channel's own built-in chat is not saved either.

Both are off until an officer turns them on for a hub. Who can read a transcript: only officers with Voice Hub Management, by default. An officer can turn on Let people who were in the channel read its transcript on the hub; then the channel's owner and anyone who was in the channel can read it too, only while they are still a member of the server. Leaving, being kicked or being banned removes you from every transcript's reader list for that server. Hubs set up before 2026-11-08 were reset to officers only — turn the toggle back on to let participants read. Deleting your account removes your messages from every transcript.

Waiting room (beta, on servers using the new control panel)

Want to vet who comes in? Press 🚪 Waiting room on your channel's control panel. The bot opens a second voice channel next to yours, ⏳ Waiting · <your channel>, where people can wait without being heard.

Someone joins the waiting room and a card pops up in your channel's chat: Let in or Turn away. Let them in and the bot moves them across and lets them back in later too; turn them away and they're dropped from the waiting room.
Can't see the waiting room? Lock your channel and others get an Ask to join button on the panel, or they can type /voice knock and pick you. Your card shows up the same way.
People you trust or permitted skip the queue. People you've blocked can't ask. Turned away? You can ask again in 10 minutes. A request nobody answers expires after 5 minutes. Hopping in and out of the waiting room won't ping the owner again for a minute.
If your channel is hidden, so is its waiting room — only the people you trust or permitted can see it, so its name never gives your channel away.

You can also run the waiting room from the My voice channel page on the web. Press the button again to close it; anyone still waiting is disconnected.

Event voice channels¶

These belong to an op and die with it. The event creates channels for its groups, the bot moves people around during the run, and everything is torn down when the op ends or is cancelled.

Command	What it does
`/create_vcs <id>`	Create temp channels for any of the event's teams that don't have one
`/move_event_crew <id>`	Pull every confirmed attendee into your current voice channel
`/start_op <id>`	Ping and DM signed-up members who aren't in voice yet

Time in these channels is attendance — including for walk-ins who never signed up. See Events & Ops.

Give the two systems separate categories

If your voice hubs spawn into the same Discord category your ops use as their rally point, both systems compete for that category's 50-channel limit — and whoever asks for the 51st gets turned away mid-op. The Voice Hubs page warns you when you pick a colliding category. It's a legitimate choice for a small org; it just shouldn't be a surprise.

Next: Events & Ops