How To Role in Guilded - A Guide For Everyone

The video provides a comprehensive guide to setting up and understanding roles and permissions in Guilded servers (0:00).

Here's a breakdown of the key aspects discussed:

• Accessing Role Settings: To manage roles, navigate to your server settings by clicking the drop-down arrow in the upper left corner and selecting "settings" (0:20).

• Default Member Role: Every Guilded server automatically comes with a "Member" role, which is the basic role assigned to all users, including the server owner (0:52).

• Creating Custom Roles: You can add various custom roles, such as "Mod," "Streamer," "Creator," or even roles based on subscription or XP leveling (1:06).

• General Permissions: These permissions, like "update servers," "manage roles," and "invite members," should primarily be reserved for administrators and possibly super-mods due to their potential for misuse if granted to regular members (1:47).

• Recruitment Permissions: If your server uses applications for new members, these permissions (e.g., "view applications," "approve applications") are crucial for staff to manage the recruitment process (3:10).

• Announcement Permissions: While everyone should be able to "view announcements," the ability to "create," "remove," or "manage announcements" should be limited to staff (3:49).

• Chat Permissions: Most chat permissions, such as "read messages" and "send messages," are open to all members, but "manage messages" and "manage threads" should be reserved for mods or admins (4:16).

• Calendar Permissions: If you utilize Guilded's calendar, members can "view events," but creating or managing events and RSVPs should be restricted to staff (4:48).

• Forum Permissions: Regular members can typically "read" and "create forum topics and replies," but "managing" or "locking topics" is for staff (5:28).

• Document and Media Permissions: Similar to other content, members can "view documents" and "media," but "creating," "managing," or "removing" these items should be restricted to staff (5:51, 6:00).

• Voice Permissions: Users can "join voice channels" to hear, but "add voice" (to speak), "manage voice rooms," or "mute/deafen members" should be staff-only permissions (6:17).

• Competitive Permissions: These are for managing tournaments and scrims and should be assigned to staff responsible for organizing such events (7:15).

• Customization Permissions: This includes managing emojis and nicknames. While allowing members to change their own nicknames is optional, "managing nicknames" (e.g., for inappropriate names) should be a staff function (7:36).

• Forms, Polls, Lists, Brackets, and Scheduling Permissions: These functionalities allow for community interaction but require careful management. Permissions for creating, managing, or deleting these items should generally be restricted to staff (8:09, 8:22, 8:55, 9:09).

• Bot and Server XP Permissions: These should never be granted to regular members (9:37, 9:47).

• Stream Permissions: Members can "view streams," and depending on community engagement, some can "join voice" or "set up their own streams." However, the ability to "manage streams" or "send text messages within streams" is a control option for the server owner (9:50).

• Creating and Cloning Roles: New roles can be created by clicking "add another role," giving it a title, and choosing a color (10:45). A convenient feature is the ability to clone existing roles to quickly create similar roles with minor modifications (11:03).