Cloudia

Cloudia was created to bridge gaps other bots fail to provide. With Cloudia, guild customization reaches a new level of user experience by empowering members an additional level of personal customizability. This is achieved without granting users permissions that could otherwise destroy a guild if used inappropriately.

100% free, guaranteed! Since this is hosted on Cloudflare Workers' free plan, there are currently no runtime costs faced. Donations may be introduced later, should the demand for Cloudia require paid tier Workers. The use of Cloudia will remain free, however. If you still wish to support Cloudia, consider bosoting our support server (our boosters can create their own role with Cloudia).

🧰 Features:

• Allow users to build and own custom roles in your guild without giving them MANAGE_ROLES permission. Owners can delegate managers to their role, all while still under the supervision of the guild staff.
• Custom roles can be closed, managed, invite only, or open for all to join. This is up to the custom role owner to decide on.
• Explicitly grants "0" permissions, so all new custom roles are cosmetic only.
• Set role position in guild by specifying a role to place new custom roles above.
• Give users with a custom role a specific guild role. Useful for role list "breaks" at the top of the list, signifying "Custom roles" below.

More features being considered.

🔮 Use cases:

• Community guilds created for companies can onboard Cloudia to allow company staff to maintain the official company roles quickly and efficiently. In invite-only mode, any employee in list of users can add any new user to the list. Additionally, employees can choose whether to toggle/hide this role at their own free will, in case some wish to stay anonymous at times.
  • Ex: A guild onboards Cloudia. Staff creates a custom "staff" role in invite-only mode. They add users to the role, and those users can toggle their staff role whenever they please. Additionally staff members can add other staff members to this group, even without MANAGE_ROLES permission. This can be done for multiple roles, such as "Support", "Mod", etc. if they wish.
• Guilds can reward certain users with the ability to create their own custom role for personalization.
• While standard color roles exist, this gives users limitless customizability to choose any color they wish to use at any time. With support for gradient colors, the options are exponentially greater!
• Although Cloudia does not grant permissions to custom roles, guilds can still give them permissions that they wish.
• Nothing is stored/visible on Discord to standard users, even with modded clients, so staff can go "Incognito" and hide amongst the rest. They can then toggle their staff permission when necessary to drop the hammer. Although this type of setup can be completed with other bots, it usually involves building a custom command, setting up another role to grant permission to this ability, special channels, or maintaining a list on their control panel (which is a hassle).

⚒ Setup:

1. Add the bot to your guild.
2. Use /role-admin to configure various settings for your guild (limits, log channel, new custom role placement).
3. Grant access to /role-create via Guild Settings > Integrations to allow specific members to create roles as you wish.

🔑 Permissions:

Required (will not function properly without)

1. Manage Roles - This is the core of Cloudia's purpose. It'd be silly to not include as the bot would be unable to perform its job.
2. Mention @everyone, @here, and All Roles - Cloudia tags roles in messages (silently, does not notify them) for convenience.
3. Send Messages - Standard, used for logs. All interactions are ephemeral otherwise.
4. View Channels - Standard, needs to be able to interact somewhere.

Suggested (possible future features/use)

Add Reactions
Attach Files
Create Invite
Create Private Threads
Create Public Threads
Deafen members
Embed Links
Manage Channels
Manage Webhooks
Move Members
Mute Members
Read Message History
Send Messages in Threads
Use External Emoji
Use External Stickers
View Audit Log

Optional (may never use)

Manage Nicknames
Use Activities
Use Application Commands
Use External Apps

ℹ Additional Information:

• Cloudia is a webhook-only based bot. In other words, getting certain information, such as role given/taken/deleted alerts is not possible. This operates in a passive mode. We have no plans to add gateway support for such events, and thus any "lockdown" features cannot be added. There are other bots that can be combined with Cloudia for this level of detail. At the end of the day, Cloudia is a utility bot, not a moderator/police. It is ultimately up to the guild and custom role owner to maintain control of the role as they wish.
• This is not a basic role menu bot (colors, labels, etc.). If you want to offer users the ability to add custom roles as "labels", use Discord's built-in onboarding features. This is specifically to allow users the ability to choose custom label/color on their own. Think of "clans" in your guild.
• Custom role lists (management and user) will not be linked to other roles. We feel that this level of control is out of scope for Cloudia and the gap is already filled by other gateway powered bots (i.e. allow users with role x to use command to togggle role y).
• We reserve the right to block any guild/user we feel is abusing Cloudia (ex. spamming commands and triggering rate limits) by any means we see fit.

🛡 Our stance on privacy and security:

• Protecting our users is our biggest concern. We do not collect or store any data that is not absolutely required for operation.
• NEVER give your bots Administrator permission, including ours. This is for the safety of your guild and its users. We have included a list of all permissions needed, as well as justification for each, in order to ensure you are practicing the principle of "least privilege". Some of these will always be required, while others are suggested (you may miss out on current/new features without them).
• No guild messages are ever read as there is no gateway connection and webhook bots will not receive such content.
• We will NEVER request your email attached to your Discord account as this is seen as unnecessary and invasive. If for some reason we ever need an email address in the future, we will ask for this to be provided.
• External Discord data collected:
  • User IDs
  • Guild IDs/Names
  • Role IDs
• Per Cloudflare: All data is encrypted at rest (EAR) and in transit (EIT).

If you suspect malicious use or would like to report a security risk, please join the Discord support server and feel free to share/DM concerns.