Roles and permissions reference

Roles group permissions so users receive the access they need in an office. Use the system role that most closely matches a user's responsibilities, or create a narrower custom role.

System roles

• Admin: broad operational access to the dashboard, statements, payment runs, Books and enabled Fixed Term Deposit functions.

• Profile admin: manages interest pools, interest and payout profiles, standing rates, bank profiles and Books; can also view the dashboard and History.

• Profile viewer: read-only access to interest pools, interest and payout profiles, bank profiles and Books.

• Office admin: manages users, roles and the current office's settings, and can view History.

• Organisation admin: includes Office admin access and can manage Organisation Settings and API tokens.

• Approver: can view supporting statements, Books, payment runs and Fixed Term Deposits and approve the supported workflows.

Permission categories

Permissions are grouped by responsibility, including General, Statements, Payment runs, Books, Interest pools, Interest profiles, Payout profiles, Standing rate profiles, Fixed Term Deposits, Users & roles and Settings. A page may also require its office feature to be enabled.

Office scope

Roles are evaluated in the current office. A user can therefore have different access in different offices. Organisation admins can work across the organisation and are automatically added to newly created offices.

Where managed-entity permissioning is enabled, a role controls what the user can do and a direct or team assignment controls which client records are in scope. Granting a team assignment does not add action permissions, and granting a role does not bypass the record assignment.

Custom roles

Custom roles belong to an office and can combine only the permissions needed for a responsibility. Changes affect every user assigned to that role, so review the user list before saving.