Proper separation and management of voice channels with role-based permissions #6

New Issue

myxelium · 2026-03-23T15:05:02Z

myxelium commented

2026-03-23 15:05:02 +00:00

As a server owner, admin, or authorized user,
I want all voice channels (including existing ones like “General” and “AFK”) to function as independent channels and be able to create, rename, and delete channels,
so that users can be managed correctly within each channel and the server structure is flexible and scalable.

Acceptance Criteria

All voice channels (including General and AFK) are:
- Treated as separate entities in the backend
- Able to independently manage connected users
Users can join, leave, and be moved between channels without conflicts
Owners, admins, or users with proper roles can:
- Create new voice channels
- Rename existing voice channels
- Delete voice channels
Permission system ensures:
- Only authorized users can manage channels
- Access to channels (join/speak/view) is role-based
Changes to channels are:
- Reflected in real time for all users
- Persisted across sessions
Existing channels (General, AFK) behave identically to newly created channels in terms of functionality

Definition of Done

All voice channels operate independently
Channel management actions (create, rename, delete) work correctly
Role-based permissions are enforced consistently
Default channels should by default be accessable by anyone unless changed (General and AFK)
No shared state or conflicts between channels
Feature is tested with multiple users across different roles

> As a server owner, admin, or authorized user, > I want all voice channels (including existing ones like “General” and “AFK”) to function as independent channels and be able to create, rename, and delete channels, > so that users can be managed correctly within each channel and the server structure is flexible and scalable. --- ### Acceptance Criteria * All voice channels (including **General** and **AFK**) are: * Treated as separate entities in the backend * Able to independently manage connected users * Users can join, leave, and be moved between channels without conflicts * Owners, admins, or users with proper roles can: * Create new voice channels * Rename existing voice channels * Delete voice channels * Permission system ensures: * Only authorized users can manage channels * Access to channels (join/speak/view) is role-based * Changes to channels are: * Reflected in real time for all users * Persisted across sessions * Existing channels (**General**, **AFK**) behave identically to newly created channels in terms of functionality --- ### Definition of Done * All voice channels operate independently * Channel management actions (create, rename, delete) work correctly * Role-based permissions are enforced consistently * Default channels should by default be accessable by anyone unless changed (General and AFK) * No shared state or conflicts between channels * Feature is tested with multiple users across different roles

myxelium added this to the Zoracord 1:1 project 2026-03-23 15:05:02 +00:00

myxelium moved this to To Do in Zoracord 1:1 on 2026-03-23 15:06:03 +00:00

myxelium moved this to In Progress in Zoracord 1:1 on 2026-03-29 23:26:12 +00:00

myxelium referenced this issue

2026-03-30 02:56:14 +00:00

Restructure #9

myxelium moved this to Done in Zoracord 1:1 on 2026-03-30 02:56:50 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: myxelium/Toju#6