Server settings: what admins decide
The Yeonhee bot has no slash commands for server settings. Every setting a server admin can change is on the 설정 (settings) screen of the web dashboard.
This page explains how to get to that settings screen and covers two sections in detail: DJ 권한 (DJ permission) and 기본 권한 (default permissions). The other items each have their own page.
What you can set
| What you can set | Where you set it | Details |
|---|---|---|
| Which roles count as DJ | Dashboard settings screen | Below on this page |
| Permission level for 8 actions | Dashboard settings screen | Below on this page |
| Which channel the controller message appears in | Dashboard settings screen | Pinning and combining the controller message channel |
| Server volume and volume sync | Playback screen and commands; sync is set by the operations team | Volume policy and volume sync |
| Whether to use Premium (sub-bots) | Request it from the operations team | Turning on Premium (sub-bots) |
| Who can open the dashboard | Discord roles | Who can use the dashboard |
If you want to open specific commands only to certain roles, that isn't a Yeonhee setting. You do it in Discord under Server Settings → Integrations → Yeonhee.
Getting to the settings screen
- Log in to the dashboard with your Discord account.
- Choose the server you want to configure in the left sidebar.
- Press your avatar on the right of the header to open the user menu, and select 설정.
The settings item isn't in the sidebar. It's only in the user menu. And if you don't have Administrator permission on that server, the menu item itself doesn't appear. If you switch to a server where you aren't an admin while the settings screen is open, the screen automatically goes back to "지금 재생" (now playing).
TIP
Most "I can't see the settings menu" questions come from people who only have Manage Server (ManageGuild) permission. Yeonhee's settings screen requires Administrator permission, not Manage Server. For the full access conditions, see Who can use the dashboard.
8 actions × 4 permission levels
The default permissions section is a grid where you assign one of 4 levels to each of the 8 actions. The on-screen labels and initial values are as follows.
| On-screen label | Initial value | Description |
|---|---|---|
| 볼륨 조절 (volume control) | DJ 이상 (DJ or higher) | Change the server-wide volume |
| 다음 곡 (next song) | 신청자 이상 (requester or higher) | Skip the current song |
| 이전 곡 (previous song) | 신청자 이상 | Go back to the previous song |
| 일시정지/재생 (pause/play) | 모두 (everyone) | Switch playback state |
| 정지 (stop) | DJ 이상 | Stop playback and clear the queue |
| 탐색 (seek) | DJ 이상 | Move the playback position |
| 반복 모드 (repeat mode) | DJ 이상 | Switch between single-song and queue repeat |
| 셔플 (shuffle) | DJ 이상 | Shuffle the queue order |
A server where no one has ever touched these works with the initial values above. How volume and seek look from the user's side is covered in /볼륨 · /탐색 (volume, seek).
How the 4 levels are actually checked
They're checked in order from the top.
- If you have Administrator permission, you pass regardless of the settings. You can't block admins with "관리자만" (admins only).
- If the level is 모두 (everyone), you pass.
- If the level is DJ 이상 (DJ or higher), you need at least one DJ role.
- If the level is 신청자 이상 (requester or higher), you need a DJ role, or you must be the person who requested the song playing now.
- If the level is 관리자만 (admins only), everyone who didn't pass in step 1 is refused.
Here, "requester" means the requester of the song playing at the moment you try the action. Even if you added another song in the queue, if the song playing now is someone else's, you can't use actions set to "신청자 이상."
TIP
"관리자만" is effectively the same as "only people with Administrator permission." If you want to allow specific people besides admins, the right way is to give them a DJ role and set the level to DJ 이상.
Registering DJ roles
In the DJ permission section, the server's roles are listed as chips. Press them to turn them on or off. You can choose several at once, and having just one of them is enough to count as a DJ.
Two kinds of roles don't appear in the list.
@everyone- Roles created automatically by other bots or integrations, such as the Nitro Booster role and roles dedicated to other bots.
WARNING
If you set a DJ role but no one is recognized as a DJ, the role you set has most likely been deleted in the meantime. If a chip that was on has disappeared when you reopen the settings screen, that role no longer exists on the server. Create a new role and set it again.
These settings apply the same way to Discord and the dashboard
Permission settings aren't dashboard-only. Slash commands, controller buttons and dashboard buttons are all checked against the same rules.
Queue actions in the dashboard don't have their own items. They're tied to the existing 8.
| Dashboard action | Permission needed |
|---|---|
| Clear the whole queue | 정지 (stop) |
| Remove one song from the queue | 다음 곡 (next song) |
| Reorder the queue | 다음 곡 |
| Jump to a specific song | 다음 곡 |
Actions permission settings can't block
The 8 default permissions only cover actions that control music that's already playing. There are no settings for calling the bot in, making it leave, or adding songs.
WARNING
/들어와 (join) · /나가 (leave) · /재생 (play) · /검색 (search) · /다음재생 (play next) aren't affected by permission settings. Not supported So even if you set "정지" (stop) to DJ or higher, anyone in the same voice channel can make the bot leave with /나가. If you want to open these commands only to certain roles, limit each command's permissions in Discord under Server Settings → Integrations → Yeonhee.
Extra conditions that differ by route
Even after passing the permission level, one more condition applies depending on the route. This difference is why people ask, "It works in Discord but not in the dashboard."
| Route | Must you be in a voice channel | Must you be in the same room as the bot |
|---|---|---|
| Slash command | Yes | The target bot is chosen based on the channel you're in |
| Controller button | No | No |
| Dashboard action | Yes | Yes |
TIP
Controller messages can be pressed from outside a voice channel. If the controller is in a channel anyone can enter, "정지" (stop) may keep getting pressed. The practical fix is to pin the controller to a specific channel and restrict who can view that channel. See Pinning and combining the controller message channel.
Changes apply only when you press save
When you press chips and buttons, the change happens only on the screen at first. 저장되지 않음 (not saved) appears in the top right, and the change actually applies only when you press the 저장 (save) button.
When you save, the controller message is deleted and created again. Even if you only changed permissions, the controller comes back up at the bottom of the channel, so don't be surprised.
WARNING
Unsaved changes disappear without warning the moment you switch servers. They're reset both when you pick another server in the sidebar and when you move to another voice channel and the dashboard automatically follows you to that server. The symptom is: "I pressed a few chips, looked at another server, came back, and it was back to 저장됨 (saved)." While 저장되지 않음 is showing on the right of the header, don't switch servers. Press 저장 first.