Permissions
Overview
Permissions is where you control your staff's access — what each team member can see and do in the operator portal. It has two parts:
| Page | What it does |
|---|---|
| Roles | Define named bundles of permissions (e.g. Support, Full Access, Read only). |
| Login Accounts | Create the staff sign-in accounts and assign each one a role. |
The idea is simple: a Role is a set of permissions; a Login Account is a person, assigned one Role. Change a role and everyone with that role is updated at once.
How access is decided
Every action in the portal — opening a page, seeing a menu item, clicking a button, editing a field — is governed by a permission. In the Role editor, permissions are laid out as a grid:
- Modules (rows) — the areas of the system: Subscriber, Invoice, Payments, OLT, ONU, Ticket, Inventory Item, Config, and so on.
- Permissions (checkboxes) — the actions within each module: Add, List, Show, Update, Delete, plus module-specific ones like Rollback, Poll, Assign, Show All Tickets.
A staff member sees a menu or page only if their role has the matching permission. Throughout this documentation, the Required Permissions section on each page names them in this Module → Permission form (for example, OLT → Add, or Other Dashboard → Inventory Dashboard) — exactly as they appear in the Role editor.
:::note Related settings Permissions control staff access. Two related areas are configured elsewhere:
- What your customers can do in their portal — see Config → Subscriber Portal.
- Privacy permissions (who can see a subscriber's mobile/email/address, and who can export data) appear as their own module in the Role grid. :::