Roles and permissions in Voxara

Who can do what, and where.

How it fits together

Every member has the @everyone role, which sets the baseline for the whole space. On top of that you create roles and give them to people; a role can grant permissions the baseline does not have. Then each channel or category can override the result for that place only, allowing or denying a permission for a role or for everyone.

The order is: baseline, then roles, then category overrides, then channel overrides. A channel override wins. At any one level, an explicit allow for one of a member's roles beats a deny for another. The space owner bypasses all of it, always.

Making moderators

Space settings, Roles, New role. Name it Moderator, pick a colour, and turn on the moderation permissions you want: manage messages (delete, pin, lock threads, curate forum tags), time out, kick, ban. Save, then open a member's profile or the Members tab and give them the role. Moderators are exempt from slow mode and can see reports.

A read-only channel

Right-click the channel, Permissions. Under @everyone set Send messages to deny (the X). Then add your Moderator or Staff role and set Send messages to allow for it. Members see the channel and its messages but their message box reads "You do not have permission to send messages in this channel".

A private channel

Same dialog: set View channel to deny for @everyone, then allow it for the role that should see it. Members without that role do not see the channel in the sidebar at all, and the server refuses them if they try another way.

Checking your work

Because the owner bypasses everything, test with a second account or ask a member. Changes apply instantly; nobody has to reconnect.

More guides: Create a space, Create channels, Invite friends, GitHub webhook. Building a bot? The bot documentation covers the API.