# Discord rework 1- **Newcomer 🌱** Get to know the people in the community 2- **Buidler πŸ—οΈ** Find resources and share your work 3- **Early Adopter πŸŒ…** Join the pioneers in the ecosystem 4- **Governance πŸ›οΈ** Take part in decision making processes 5- **Academia & Research πŸ§‘β€πŸ”¬** Deep discussions between researchers 6- **Speculation/Degen 🦍** Markets, altcoins and degens 7- **Unlock everything ♾️** Just like the old times ## Standard to unlock - IOTA FOUNDATION OFFICIAL - Category Role Settings: @Member: View Channels - START HERE - Category Role Settings: @Member: View Channels - Channels Role Settings: @Member: remove writing rights in specific channels like learn-the-rules, etc... - Discussion ## 1- **Newcomer** - Hangout - Ecosystem ## 2- **Buidler** - Node Software - Wallet Software - Dev Community - Smart Contracts - IOTA Projects - Team UP - Ecosystem - GITHUB FEEDS ## 3- **Early Adopter** - Hangout - Ecosystem - Wallet Software - IOTA Projects - Dev Community - GITHUB FEEDS ## 4- **Governance** - Hangout - Governance ## 5- **Academia & Research** - Research & Academia ## 6- **Speculation/Degen Stuff** - Hangout - Degen Space - Ecosystem - GITHUB FEEDS ## 7- **Unlock everything** - ALL ## Get your badges Additionally add/remove every single category by pushing a button to tailor the Discord # Walkthrough ## Alt account verification ## Let's go 1. Select your interests ![](https://i.imgur.com/4J8TKAg.png) 1. Select Notifications - Events - Surveys ![](https://i.imgur.com/oZ8rCcW.png) 1. Why did you join - **TO BE REMOVED** ![](https://i.imgur.com/RpTR6jK.png) 1. Referral - add LinkedIn - add CoinMarketCap ![](https://i.imgur.com/VTWq8gC.png) # TODO - List of categories and roles connected to them - Create Categories # Discord roles Newcomer ## Roles changes Rename Members to TouringTest Access to getting_started only for Onboarding role # Welcome messages By chosing one or more roles the user is welcome with a reply in a thread IF and only if the user writes a message in the #introduce-yourself channel ![](https://i.imgur.com/P9kqlfr.png) ## All Categories **Don't wanna miss a thing, eh?** Get ready to unlock the whole potential of the server. πŸ‘‡ ## Newcomer 🌱 **Hello and welcome to your community** - Browse the channels and feel free to ask questions to learn more - Not all activitiy is visible right now. Get dedicated roles to unlock more channels in <#884705920028930068> (#get-your-badges) ## Buidler πŸ—οΈ **Ready to buidl?** We suggest to start with the wiki at <https://wiki.iota.org>. - Currently you may be interested in Stardust, the first iteration of the Shimmer innovation network with support for a multi asset DLT. <https://wiki.iota.org/introduction/develop/welcome>. - For a quick start have a look at our tutorial section: <https://wiki.iota.org/tutorials> ## Early Adopter πŸŒ… **The early bird catches the worm** - Hangout with the community, explore and try out upcoming dApps and opportunities. - Explore ecosystem projects: <https://shimmer.network/ecosystem> - Be informed about the newest development proposals early, have a look at our Tangle Improvement Proposals (TIPs) repo https://github.com/iotaledger/tips - Already heared about our Touchpoint initiative to build, launch and scale the next generation of dApps and infrastructure? Learn more: <https://assembly.sc/touchpoint> ## Governance πŸ›οΈ **Ready to take matter in your own hands?** The community is empowered to take part in governance. Start participating in key decisions at our governance forum <https://govern.iota.org> ## Academia & Research πŸ§‘β€πŸ”¬ **We build on the shoulders of giants** Research is a key element to the project. - Have a look at our research papers https://wiki.iota.org/research/research-papers - Keep yourself up-to-date with the latest coordicide specs https://wiki.iota.org/IOTA-2.0-Research-Specifications/Preface And join the discussion in <#970953102503071780> ## Speculation/Degen 🦍 **Ready to ape in?** - Take off your shoes and join <#970953101894889530>. Where big 🧠 start as degens 🦍 and become regens (And don't forget to give *p* bot some love) - Discuss other projects eloquently in <#970953101894889531> ## Typical Category permissions Give the role that passed the verificaion writing rights, but no viewing rights ![](https://i.imgur.com/OPchbUj.png) Give the specific role only viewing rights ![](https://i.imgur.com/gw8igeF.png) ## Last thing to do Remove all rights besides Read Message History from TuringTestPassed once AllCategories role has the necessary rights ## Categories permissions - [X] IOTA Foundation Official - [X] Start Here - [X] Staff - [X] Logs - [X] Discussion - [X] Hangout - [X] Degen Space - [X] Ecosystem - [X] Team Up - [X] Wallet Software - [X] Research and Academia - [X] Education - [X] Smart Contracts - [X] Governance - [X] Dev Community - [X] Node Software - [ ] DevEx and Education :warning: waiting for Dr. Electron - [X] IOTA Projects - [X] Github Feeds ## Categories to move to new position - Wallet Software - Research - Smart Contracts - GitHub feeds - Xteams - Wallet # Permission resources > The problem is that, intuitively, people are adding roles to each channel and ticking the green check box to enable chat. That's the problem. We are not supposed to do that. We are supposed to set that in default role permission that applies across the server and not even worry about having to set that in each channel. Permissions within a channel should almost always be the neutral "/" option. "/" means that a default server-wide setting is being applied. So, if you gave a role a default permission to chat, then "/" means they can chat in all channels they have access to on your server. I can see why Discord did this because once you learn how this works, it's easier because you don't have to micromanage permissions for each channel. As for mute, for as long as the permission inside the channel is "/", when you add a mute role and select "X", it will work because the neutral "/" always yields to "X". In a nut shell, if you are checking that green check mark on prime roles inside your channels, you need to change that to "/" and make sure that prime roles have permission to chat by default. Then, a mute role will work as it should.