Community On-boarding requires unprotected servers. There is no consideration for role-protected servers
Community On-boarding requires unprotected servers. There is no consideration for role-protected servers.
FIVE channels that @everyone can talk in? C'mon Son!
Every task requires @everyone permission be granted.
This is unsafe. We have to setup little hacks around this like making 5 public channels for @everyone but hiding them from the role'd up users. Setting task destinations that don't have the loose perms it requires and hoping we can push it through without it erroring out.
We should not be forced to do this, forced to weaken our security and unprotect parts of our servers, to take advantage of an aesthetically pleasing feature, that does not actually need those requirements.
Some of us know how to actually use discord and setup granular RBAC systems properly. Please allow educated admins to use this feature.
-
Let us decide which features of onboarding to turn off or on, with a toggle.
Most servers are protected and would just need the questions for roles and/or channels.
The channels should NOT require @everyone permission, especially since the DEFAULT task is to read and agree to rules, which would give them the role(s) they need to take action in the channels we offer from the on-boarding questions.
Default channels should also not require @everytone, since they will go through the task (agree to rules) that will give them the role(s) needed. However providing a toggle to turn the feature off is acceptable for role protected servers. Forcing us to create 5 channels that @everyone can speak in, just to hide them from members who have the role they get after agreeing to rules is not.
2
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar