Modra

ACCESS & PRIVACY

Give each person only the access they need.

Modra maps Discord roles or individual members to dashboard access groups. Access to the dashboard never grants additional Discord permissions by itself.

Recommended access groups

Community owner

Full community configuration, branding, modules, billing, and access administration.

Community manager

Module setup and operational records, without billing or owner-only controls.

Reviewer

View and action assigned ticket or application categories without changing setup.

Moderator

Moderation, safety, audit, and approved ticket access appropriate to the role.

Create an access group

  1. Open Dashboard access.The owner, or a group explicitly allowed to manage dashboard access, can open this page.
  2. Create and name the group.Use a purpose-based name such as Application Reviewers instead of a person's name.
  3. Select capabilities.Separate view, action, configuration, and access-management permissions wherever available.
  4. Add Discord roles or members.Role mappings update access as staff roles change. Individual assignments are useful for temporary testers.
  5. Test with the actual user.Ask them to sign out and back in if their Discord roles changed, then confirm hidden pages and restricted categories stay hidden.

Important boundaries

  • Dashboard page visibility is permission-aware, but Discord buttons and slash commands are checked separately.
  • Ticket and application categories can be restricted to different staff roles even when those staff share a broader module permission.
  • A user who can review records does not automatically receive permission to edit that module's setup.
  • Deleting an access group removes that mapping; it does not delete the Discord role.
  • Modra support has no standing access. The owner must grant explicit, time-limited support access when help is needed.

Ticket, application, and appeal category scope

  1. Grant page access.View Tickets, View Applications, or View Appeals makes that workspace available, but does not bypass its category filters.
  2. Assign category viewers.In the module setup, add the Discord roles that may see each category. A reviewer only sees records whose category matches one of their current roles.
  3. Assign category action roles.Add the roles that may reply, review, approve, deny, or otherwise action that category. They also need the corresponding dashboard action permission.
  4. Reserve all-category permissions.View All and Action All bypass category roles and should normally be limited to owners or senior community managers.

Configure Tickets, Applications, and Appeals separately. A person can review one category while having no access to unrelated records or modules.

Owner safety check

Keep at least one owner-controlled account with access administration. Review groups after staff departures or major role changes.