Permission Hierarchy
Invaro uses a three-tier hierarchy for portal access:- 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
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.Setting Up Permissions
Open the Permissions page
Navigate to Permissions in your portal dashboard. You must be a portal Owner or Admin.
Choose a source type
Select whether this Access Role is based on a Discord Role or an Invaro 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.
Select the role or team
Use the dropdown to pick the specific Discord role or Team this Access Role applies to.
Set a display name and priority (optional)
Give the Access Role a friendly display name (defaults to the role/team name). Set a priority number — higher numbers win when a member matches multiple Access Roles.
Configure page permissions
Expand Page Permissions to configure which pages this Access Role can access. For each page, you can grant any combination of:
Click the checkbox on the left of each page row to toggle all permissions at once for that page. Individual permission pills can be toggled independently.
| Permission | What it allows |
|---|---|
| View | See the page at all |
| Edit | Modify existing content |
| Create | Add new entries |
| Delete | Remove entries |
| Manage | Full control over all entries |
Configurable Pages
The following pages support Access Role permissions. Pages marked as always visible (like the Overview or Dashboard home) are accessible to all portal members regardless of Access Roles. Owner/Admin-only pages (like Settings and API Key management) cannot be delegated. Pages you can configure access for include: Binds, ModMail, Tickets, Member Stream, Team Directory, Triggers, Audit Logs, and more — depending on your portal’s enabled features.Managing Access Roles
Each Access Role card shows the role’s name, type (Discord or Team), priority, and which pages have permissions configured.| Action | Description |
|---|---|
| Toggle | Enable or disable the Access Role without deleting it. Disabled roles are ignored during access checks. |
| Edit | Update permissions, display name, or priority. |
| Delete | Permanently removes the Access Role. |
Tips
- Set higher priority numbers for senior staff roles so their permissions take precedence over junior roles.
- You can stack multiple Access Roles — a member who holds two Discord roles that each have an Access Role will benefit from the highest-priority one.
- Owners and Admins always bypass Access Roles entirely — you cannot restrict them through this system.
