Networking and community are essential for growth for any streamer and there is no better/easier way to accomplish this than by having your own Discord server. I have my own and it’s quite busy, between all my followers, subs, admin, stream team, random images, and just over sass. You are more than welcome to join it by clicking here. When you enter in a new discord always look for the rules text channel and make sure you are aware of the server rules before you start engaging with the community. Some servers are more strict than others. I’ve asked The GamingDaddies to explain how they have set up their discord settings as Kendo has a lot of expereince with this. If you have questions, feel free to tweet to them, or join their discord server and post your questions there.
As most of you know Brain and Kendo are developers working for hospital information systems. Kendo has been working in this field since his first job after school, and he was working on how to setup permissions in areas with very high privacy policies, because nothing is worse than published patient related data in hospitals!
Thats the reason why he setup our permissions in our discord server. So we wanted to give a short explanation on how our permission-strategy works and why is it like that.
Let me share an example with you.
Let's say we have the following settings:
- We have admins (only the streamer plus 1-2 people with a lot of security awareness)
- We have mods (maybe some stream mods are discord admins as well)
- We have subs (like Kitty's Knights, or our Close Family)
- We have followers
- We have new people (people who are in discord and not assigned to a role which means this is the @everyone group without another group-assignment)
Here are the requirements:
- We need a Welcome Hall (so new people can say hello)
- We need a News/Announcement channel (to keep the community up to date)
- We need a chat for all our followers (to keep the community alive)
- We need a Subs-Only-Chat (to give them the feeling to be closer to the streamer)
- We need a chat for our mods/admin (to keep the them up to date)
- We need voice chats for at least: one for everyone, one for the community, one for admin/mod meetings
First of all we need to setup the roles by default. Therefore the one thing that is really important is that we made our permissions additive; which means a user is assigned to his current role PLUS everything below.
So the handling is like this:
If you join the server you’ll be automatically in the @everyone group with no real assignment (discord default) If you are a follower we’ll assign you the role “Follower”. If you are a Sub as well, then you’ll be assigned to “Follower” AND “Subs”. Next step: if you are a Mod you’ll have assigned “Follower”, “Subs” AND “Mods”
Now some of you will ask “Why?” The reason is rather easy, we don’t like to do work twice. I don’t think anyone does, and because of this now most of the configuration can be done in a really easy way.
Let's continue with the Text Channels:
Welcome Hall: here we have @everyone set to “write, read” and disabled Message History: This means a new Member can say “Hello” in there but does not see “When” someone else joined the server.
The only Role which is permitted with the “Message History” is e.g.: Mods Which means Mods and Admins are able to read the history to grant the new User the permission he deserves ;-)
Except for the welcome hall, we have to set the @everyone permissions in the other chats to prohibit everything!
Announcements/News Channel: In here the Follower Role gets the Permission to Read + Read History. Only the Admin/Streamer is allowed to write, pin messages and mention @everyone in there. So every Follower (or higher) is able to read the news and keep up to date.
Follower Channel: We call ours the “Kindergarten” room. In here the Follower role gets read, write, read history, maybe add links and files or somehow, and maybe we want that our subs are able to create invites. The Admin/Mod role gets the permission to manage messages. So if someone writes something it can’t be edited to change the meaning of a conversation!
With knowing those few things it should be no problem to setup the other channels we mentioned as requirements.
Voice channels are working in the same way as text channels.
The last and maybe most important thing regarding of security and “Keep your discord clean” is: the General Permissions for roles in the Server Settings.
This is where you need to be very sure whom you can trust and are those guys hacker-safe. We would only give the Admin-Group the rights of “Administrator” and Manage Channel permissions. Nobody should have the Manage Roles permission, except you have an administrator of whom you would trust the same as you trust yourself.
That is more or less the basics of permissions.
Kendo was talking to a few other discord server owners outside of the streaming-scene, and there are servers out there (also from bigger companies) which are configured in a similar way; which is encouraging to us. Kendo also noticed that there are a huge amount of discord servers which are lacking in security and have little to no permission configurations.
To sum things up we’ve put a short overview of how we think permissions should be handled:
- Create and assign your roles additive
- Restrict the @everyone permission to only be able to write in one channel
- Don’t give your mods the permissions to hijack your server
- Did we say it is better to do role additive? :)
This is just our way to manage permissions and it does not mean everyone has to do it the same. Kendo set ours up like this because he has experience working in high security areas.
Some of you may remember the big Discord update where twitter was flooded with messages to check your discord permissions; where the “Administration” setting was added. Since we had our permissions set up in the additive format we didn’t need to fix our permissions!
Thank you Kendo and the other GamingDaddies who took the time to write this up. I know setting up discord server permissions can be quite intimidating to some people; I know it was for me at first!
Until next time…