Permissions

Understanding how permissions work in Marsha is essential for proper setup and security. This guide explains the permission system and how to configure it.

Discord Permissions

Marsha requires Administrator permission to function properly.

Why Administrator?

The Administrator permission allows Marsha to:

• Manage roles for mutes and auto-moderation
• Kick and ban members when necessary
• Manage channels for anti-raid features
• Delete messages for auto-moderation
• Access all channels for comprehensive logging

Role Hierarchy

Marsha can only manage members whose highest role is below Marsha's role in the hierarchy.

Setup

1. Go to Server Settings → Roles
2. Drag Marsha's role above all roles you want it to manage
3. Keep it below Administrator roles for safety

Important

If Marsha can't perform an action, check that its role is positioned correctly in the role hierarchy.

Command Permissions

Control who can use Marsha's commands through role groups.

Role Groups

Role groups allow you to assign command permissions to specific roles:

1. Go to Dashboard → Role Groups
2. Create a group (e.g., "Moderators")
3. Add Discord roles to the group
4. Assign command permissions to the group

Learn more about Role Groups →

Default Permissions

By default:

• Moderation commands (warn, kick, ban): Administrator only
• Information commands (user, server): Configurable via role groups
• Utility commands (archive, reminders): Everyone

Dashboard Permissions

Access to the web dashboard is determined by Discord permissions.

Who Can Access?

Users with Administrator permission on the server can access the dashboard for that server.

What Can They Do?

• View all settings and configurations
• Modify auto-moderation rules
• Review logs and statistics
• Configure sanctions and anti-raid
• Manage role groups

Security Recommendations

1. Limit Administrator Access

Only give Administrator permission to trusted team members. Use role groups for regular moderators.

2. Position Marsha's Role Correctly

Place Marsha's role high enough to manage members, but below owner/admin roles.

3. Regular Permission Audits

Periodically review:

• Who has access to the dashboard
• Which roles are in moderator groups
• Marsha's role position in the hierarchy

4. Use Role Groups

Instead of giving everyone Administrator permission, create role groups with specific permissions for different team levels.

Troubleshooting

"Missing Permissions" Error

Cause: Marsha doesn't have the required Discord permission.

Solution: Ensure Marsha has Administrator permission.

"Cannot manage this member"

Cause: The target member's role is higher than Marsha's role.

Solution: Move Marsha's role higher in the role hierarchy.

"You don't have permission to use this command"

Cause: Your role doesn't have permission for this command.

Solution: Ask an administrator to add your role to the appropriate role group.

Need help with permissions?

Join our support server for personalized assistance with your permission setup.