Back Office Security

Role-Based Access Control

Give every Back Office administrator the access required for their role, while keeping sensitive actions restricted by default.

Add administrator Back Office
Full name
Olivia Taylor
Role
Compliance

View users, accounts, and transactions

Reject transactions in manual review

× Approve transactions in manual review

× Manage administrators

OWNER

Full platform access. Protected from editing or deletion.

One role per administratorClear access without overlapping permission sets.
Deny by defaultRestricted pages and actions remain unavailable.

RBAC module

Access control designed around real Back Office responsibilities

FinHost separates administrative, compliance, support, and financial duties so each team member sees and controls only what their work requires.

01

Preset operational roles

Assign Admin, Compliance, Support, Finance, or Sales according to the administrator’s responsibilities.

02

Deny-by-default access

Actions remain unavailable unless they are explicitly included in the selected role.

03

Segregation of duties

Risk review, transaction approval, and platform administration can be separated across different teams.

04

Protected Owner access

The Owner retains full access and cannot be edited, downgraded, or removed by other administrators.

05

Cleaner Back Office interface

Unavailable pages and controls are hidden or blocked, reducing confusion and accidental actions.

06

Consistent access rules

Viewing, exporting, and managing data follow the same permission logic across the platform.

Access workflow

From administrator creation to controlled access

A clear setup process keeps every role understandable from the moment it is assigned.

STEP 01

Create an administrator

The Owner or Admin adds a new Back Office user.

STEP 02

Select one role

Choose the role that matches the person’s operational responsibilities.

STEP 03

Review access

Confirm which pages and actions are available before saving.

STEP 04

Apply restrictions

Everything outside the assigned role remains unavailable by default.

STEP 05

Work inside a scoped interface

The administrator sees only the controls relevant to the role.

ADMINISTRATORS4 active
Olivia TaylorCompliance
Marco TanFinance
Sarah LeeSupport

Team administration

Assign clear responsibility from the start

Each administrator receives one role, making access easier to understand, review, and maintain.

  • New administrators are created by the Owner or Admin
  • One role is assigned to each administrator
  • Permissions are visible before the account is confirmed

Financial controls

Separate review from approval

Permission boundaries help prevent one administrator from controlling every stage of a sensitive financial action.

  • Compliance can review and reject suspicious transactions
  • Finance can approve transactions that are ready to proceed
  • Core provider and platform settings remain restricted
MANUAL REVIEW#4471
ComplianceCan reject
ComplianceCannot approve
FinanceCan approve
FinanceCannot change risk rules

Why FinHost

Control access without turning permissions into a separate project

Designed for financial operations

Roles reflect the real responsibilities of compliance, support, finance, and platform administration teams.

Sensitive actions stay separated

Different teams can review, approve, and configure critical processes without unnecessary overlap.

Simple for administrators

Access is selected through a clear role rather than a long, difficult-to-maintain checklist.

Available roles

A role for every core Back Office function

01

Admin

Manages administrators and core Back Office configuration.

02

Compliance

Reviews users, verification, risk signals, and restricted transactions.

03

Support

Accesses the information needed to assist customers without broader control.

04

Finance

Handles financial reporting, transaction approval, and operational finance tasks.

05

Sales

Supports commercial workflows without access to sensitive Back Office actions.

Related FinHost modules

Build a complete security and control layer

Contact Us



Frequently Asked Questions

What is Role-Based Access Control?
Role-Based Access Control assigns Back Office permissions according to an administrator’s role. It helps ensure that each person can access only the pages, data, and actions required for their work.
Which roles are available in FinHost?
FinHost supports Admin, Compliance, Support, Finance, and Sales roles, together with a protected Owner role that retains full access.
Can one administrator have several roles?
No. Each administrator receives one role, keeping permissions clear and avoiding overlapping access.
Who can create or edit administrators?
The Owner and administrators with the required Admin permissions can manage other Back Office administrator accounts.
What happens when an administrator opens a restricted area?
The unavailable page or action remains hidden or blocked, and the administrator is informed that additional permission is required.