Roles and permissions

Six roles, six different fields of view

Permissions are not a separate module — they are the data model. A user sees what their partner and their projects allow, and that applies to reports, search and exports alike.

Roles

Who sees what

Each role's scope comes from the hierarchy, so there are no exceptions to maintain.

System administrator

Sees every partner, project and user. Partner definitions, role assignment and system-wide settings live in this role.

  • Full data scope
  • Partner and user definitions
  • System settings

Partner manager

Sees and manages only the projects in their own portfolio. Another partner's project, meter or contact never appears on any screen.

  • Own projects
  • Own users
  • Own quotes

Project manager

Runs reading, billing and subscriber work for the projects they have been given, switching between them with the project selector.

  • Reading and billing
  • Subscriber records
  • Field task assignment

Block manager

Sees the units and statements of the block they are responsible for; blocks outside that scope stay closed.

  • Block scope
  • Unit statements
  • Reading status

Field technician

Sees only the tasks assigned to them and the meters within those tasks, on their own phone.

  • Assigned tasks
  • Index entry
  • Fault reporting

Resident

Does not sign in to the panel. Reaches their own unit's cost allocation statement through a unit-specific link.

  • Unit-specific link
  • Own statement
  • No panel access

At a glance

How scope is determined

Four things decide what a user can reach.
Number of roles
Six: system, partner, project, block, field, resident
Scope source
Partner → project → block hierarchy
People vs users
People are owners and tenants; users are those who sign in
Sensitive data
Phone, email and statement links are open only to authorised roles

Frequently asked questions

What people ask about permissions

Can everyone on our team see every project?

No. Users are defined by their role and each one sees only the projects they have been given. Resident records (people) and panel users are two separate concepts.

Can our partner manage their customer's data independently of us?

Yes. The partner hierarchy is the data model itself; each partner manages their own portfolio in their own account and sees only their own projects.

Does the posting list contain personal data?

No. The posting list contains no email address, phone number or unit-specific statement link — it is designed to be posted publicly. The delivery tracking list does carry personal data and is for management only.