// Guide
Voice Relay
Bridge a voice channel in your server to a voice channel in another server, with an approval flow on the receiving side.
Voice Relay connects a voice channel in your server to a voice channel in another server the bot is also in — a cross-server voice bridge. The source side requests a link with /voice linkadminPro, the target side approves it from an embed in their log channel, and the relay stays up until someone runs /voice unlinkadmin.
Starting a link with /voice link is a Pro feature — the source server needs a Pro (or Elite) subscription, or the command replies with an upgrade prompt. /voice unlink simply tears the relay down. The bot must be a member of both servers for a link to work.
How the approval flow works
- An admin (or a member with the configured Allowed Role) in the source server runs
/voice link. - StarBot looks up the target server's Voice Relay settings. If the target has a Log Channel configured, the bot posts an Incoming Voice Link Request embed there, showing the source server, the source channel, and who asked.
- Someone on the target side picks a destination voice channel from the select menu on that request — the Approve & Connect button stays disabled until a channel is chosen — then approves (or hits Deny).
- On approval, the relay connects the two voice channels.
If the target server has no log channel configured, there is a legacy fallback: the source admin can pass target_channel_id on /voice link to connect directly, with no approval step. Setting a log channel is the recommended path — it keeps the target server in control of what gets bridged in.
Commands
voice link target_guild_id:123456789012345678 source_channel_id:987654321098765432/voice link [target_guild_id] [source_channel_id] [target_channel_id]— request a bridge.target_guild_idandsource_channel_idare optional if you've saved defaults with/config-voice;target_channel_idis the legacy direct-connect escape hatch described above./voice unlink— stop the relay for this server and disconnect./config-voice— set your defaults and (on the target side) the approval plumbing. Run it with no options to view current settings. Options:default_target_guild_id— the server you usually link to.default_source_channel— the voice channel in this server you usually bridge out.log_channel— target side: the text channel that receives incoming link requests.approver_role— target side: the role designated to approve requests.
Dashboard configuration
The same target-side settings live on the Voice Relay card in the Features tab of your guild dashboard — toggle it on, then click Configure:
Non-admins with this role can run /voice commands
Role designated to approve incoming link requests
Where incoming voice link requests are posted
Setup
- 1Configure the target side. In the server that will receive the bridge, set a Log Channel and an Approver Role — on the dashboard's Voice Relay card, or with
/config-voice log_channel:#voice-requests approver_role:@Officers. Without a log channel, requests can't be approved. - 2(Optional) Save source-side defaults. In the requesting server, run
/config-voice default_target_guild_id:… default_source_channel:…so a plain/voice linkworks with no arguments. - 3(Optional) Set an Allowed Role. By default only Administrators can run
/voice— add an Allowed Role on the Voice Relay card to let trusted non-admins use it too. - 4Link. Run
/voice linkin the source server. The bot confirms the request was sent; the bridge goes live once the target side approves and picks a destination channel. - 5Unlink when done. Run
/voice unlinkin the source server to stop the relay and disconnect.
target_guild_id, source_channel_id, and target_channel_id are raw Discord IDs (enable Developer Mode → right-click → Copy ID). They're plain text options because they usually point at another server, which Discord's channel pickers can't reach.
Related
- Tiers & pricing — what Pro includes.
- Command reference — full argument details for
/voiceand/config-voice.