Skip to main content
The Permissions system lets you delegate dashboard access to staff members without giving them full admin control. You can create Access Roles that grant specific Discord roles or Invaro Teams the ability to view, edit, create, delete, or fully manage individual pages of your portal.

​
Permission Hierarchy

Invaro uses a three-tier hierarchy for portal access: 
Owner → Admin → Staff (Access Roles)
  • Owners always have full access to everything in the portal.
  • Admins always have full access to everything in the portal.
  • Staff only see and interact with pages their Access Roles explicitly grant them.
Access Roles do not affect Owners or Admins — they apply only to members who are neither.

​
Access Roles

An Access Role connects a Discord role or an Invaro Team to a set of page-level permissions. When a portal member has a Discord role (or team) that matches an Access Role, they gain the permissions defined in that role. If a member matches multiple Access Roles, the one with the highest priority wins on any conflict.

​
Creating an Access Role

Click Add Role in the top-right corner. This opens a full-page editor.
1

Choose a source type

Select Discord Role or Team Tag. Discord Roles are the standard choice for most servers. Team Tags are useful if you use the Team Directory system to organise staff. You cannot change the source type after creation.
2

Select the role or team

Use the dropdown to pick the specific Discord role or Team this Access Role applies to.
3

Set a display name and priority (optional)

Give the Access Role a friendly display name — defaults to the role or team name. Set a priority number — higher numbers win when a member matches multiple Access Roles.
4

Configure page permissions

The Page Permissions table shows every configurable page. For each page you can grant any combination of:
PermissionWhat it allows
ViewSee the page at all
EditModify existing content
CreateAdd new entries
DeleteRemove entries
ManageFull control over all entries
Click the checkbox on the left of each page row to toggle all applicable permissions at once. Individual permission pills can be toggled independently. Permissions that are not applicable to a given page appear greyed out and cannot be toggled.Use Toggle all in the table header to enable or disable all permissions across all pages at once.
5

Save

Click Create Role. It becomes active immediately.

​
Configurable Pages

Pages that are always visible (like the portal Overview) and pages that are Owner/Admin-only (like Settings and API Key management) are not configurable. All other pages — including Binds, ModMail, Tickets, Member Stream, Team Directory, Triggers, Audit Logs, Alliance Management, Knowledge Hub, Announcements, LOA Management, and Staff Logbook — can be delegated via Access Roles. Not every permission type applies to every page. Permissions that don’t apply are shown as unavailable and cannot be selected.

​
Managing Access Roles

Each Access Role card shows the role’s name, type (Discord or Team), priority, enabled state, and a summary of configured page permissions.
ActionDescription
ToggleEnable or disable the Access Role without deleting it. Disabled roles are ignored during access checks.
EditOpens the full-page editor to update permissions, display name, or priority.
DeletePermanently removes the Access Role.
Use the search bar to find roles by name and the type filter tabs to show All, Discord-only, or Team-only roles.

​
Tips

  • Set higher priority numbers for senior staff roles so their permissions take precedence over junior roles.
  • A member who holds two Discord roles that each have an Access Role benefits from the highest-priority one.
  • Owners and Admins always bypass Access Roles entirely — you cannot restrict them through this system.