DJ Role Permissions and Dashboard Settings Update

Beatra's latest update focuses on one of the most requested server-management improvements: clearer control over what the DJ role can actually manage. Until now, selecting a DJ role gave staff a useful moderation layer for music controls, but some behavior was less obvious than it should have been. This update makes the system easier to understand, easier to configure, and more consistent across the bot and dashboard.

The biggest change is the new DJ permissions area in the web dashboard. Server admins can now choose, one by one, whether the selected DJ role can manage playback controls, queue actions, volume, autoplay, 24/7 mode, audio effects, playback speed, search, and starting or adding music. Existing DJ control behavior stays enabled by default when a DJ role is selected, while broader options such as play and search start disabled until an admin decides to turn them on.

We also cleaned up how the DJ role is detected. Beatra now relies on the role selected in server settings instead of guessing from role names. A role simply being called “DJ” no longer grants special access by itself, which makes permissions safer and more predictable for communities with custom role setups.

The settings dashboard has been reorganized into tabs, so DJ role settings, allowed channels, prefix, auto-leave, and language options are easier to scan and edit. On the bot side, the /settings DJ panel now shows a direct localized dashboard link for the current server, helping admins jump straight to the right page without searching.

This update is available across all 21 supported languages. It is a small-looking settings update, but it gives server owners a much better foundation: fewer surprises, clearer defaults, and more control over who can manage the music experience.