Powered by MemberCheck

Bring your whole
compliance team

Unlimited users in every role except Compliance Officer, which takes up to 3 per organisation or suborganisation.

Request a Demo

Built around roles and Access Rights

Unlimited, with one cap

Add as many users as you need in every role, with up to 3 Compliance Officers per organisation or suborganisation.

The right access for each

Six roles and 18 Access Rights decide what every teammate can see and do.

One platform, every branch

Teams and suborganisations work on the same MemberCheck, scoped to their own organisations.

Six roles

Six roles, one platform

Six role types, from the Compliance Officer down, each with its own place on the permission matrix.

  1. Compliance Officer

    Up to 3

    Sets up organisations and users, scans and reviews every result, implements due diligence decisions.

  2. Advanced User

    Unlimited

    Runs scans and reviews the results of every assigned organisation.

  3. Standard User

    Unlimited

    Runs scans and reviews only the results of their own.

  4. Billing Officer

    Unlimited

    Reviews scan results and generates Activity and Due Diligence reports, no scanning rights.

  5. Data Entry Operator

    Unlimited

    Runs individual and corporate scans, single and batch.

  6. Auditor

    Unlimited

    Read only access to everything a Compliance Officer can see.

How it works

Add a teammate, five steps

The Compliance Officer invites, the account takes its role and rights, the user activates.

1

Open

Open Administration and Users

Only Compliance Officers manage users, and the console lives in Administration > Users.

  • Compliance Officer creates
  • In Administration > Users
  • Assign or invite
Add userCompliance Officer creates
Priya NairActive
Tom BeckerActive
Mei LinActive
Omar HaddadPending
Sofia RossiActive

Administration > Users

2

Create

Create the account

A unique Username and a unique Email give one account one role. Someone who needs two roles needs two accounts.

  • Unique Username
  • Unique Email
  • One role per account

Create the account

NameOmar Haddad
UsernameUnique Username
EmailUnique Email
One role per accountUnique Username
Compliance OfficerAdvanced UserStandard UserBilling OfficerData Entry OperatorAuditor
3

Assign

Assign the organisations

Pick one or many organisations and suborganisations. The same role applies across all of them, and every user needs at least 1 active organisation.

  • One or many organisations
  • Same role across them
  • A suborganisation first
OrganisationsStandard User
  • Parent organisation
  • Suborganisation A
  • Suborganisation B
Same role across themStandard User
A suborganisation first
4

Refine

Refine the Access Rights

Access Rights switch individual features on or off for that person, so the role fits the job exactly.

  • Switch each right
  • Rights follow the role
  • 18 named rights
Access RightsStandard User
ScanningSingle Scan
Results and due diligenceScan Results
DocumentsView Supporting Document
AdministrationOrganisation Management
ServicesMonitoring
Rights follow the role18 named rights
5

Activate

They set the password

The onboarding email carries the login and region details. The user sets a password and security question, and Pending becomes Active.

  • Password and security question
  • Pending becomes Active
  • Role in My Profile
PendingActive
Omar HaddadStandard User
  • Chosen by the user at activation
  • Lockout after failed attempts
  • Role in My Profile

Who can do what

The feature permission matrix

What the six roles can run, view and manage.

  • Run single scans for individualsFull access
  • Run batch scans for individualsFull access
  • Run corporate single scansFull access
  • Run corporate batch scansFull access
  • View scan results run by othersFull access
  • Perform due diligenceFull access
  • View reportsFull access
  • Manage Users (add, edit, deactivate)Full access
  • Manage Organisation (add, edit, deactivate)Full access
Full accessView onlyNo access

Standard Users perform due diligence and run reports on their own scans only. Auditors see every Compliance Officer feature without changing anything.

Growing

Grow across teams and branches

Departments and branches take suborganisations, each with its own officers, settings and users, all under one structure.

1

Branch

Create a suborganisation per team

The parent Compliance Officer sets up suborganisations for departments or for specific scan criteria, flat and wide or deep and nested.

  • One per team or branch
  • Own scan settings
  • Flat or nested
Create a suborganisation per teamSuborganisation
Parent organisation
  • A
  • B
    • B1
    • B2
  • C
    • C1
Own scan settings
One per team or branchFlat or nested
2

Officers

Give each branch its own officers

Every organisation and suborganisation takes up to 3 Compliance Officers, and different ones per branch suit different work.

  • Up to 3 per branch
  • Different officers per branch
  • Inactive ones do not count
Compliance OfficersUp to 3
Parent organisation
  • A
  • B
    • B1
    • B2
  • C
    • C1
  • Parent organisationUp to 3
  • AUp to 3
  • BUp to 3
  • CUp to 3
  • B1Up to 3
  • C1Up to 3
  • B2Up to 3

Inactive ones do not count

3

People

Assign users across branches

A user belongs to one or many organisations and suborganisations and keeps the same role on each.

  • Many organisations, one role
  • Two roles, two accounts
  • Create the branch first
Mei LinUnlimited users
Parent organisation
  • A
  • B
    • B1
    • B2
  • C
    • C1
AMany organisations, one roleStandard User
BTwo roles, two accountsStandard User
CCreate the branch firstStandard User
4

Scope

Visibility follows the hierarchy

The parent Compliance Officer sees every branch below them, while a suborganisation officer sees that branch and its children.

  • Parent sees A, B, C, B1, C1, B2
  • CO of B sees B, B1 and B2
  • CO of A sees only A
Visibility follows the hierarchyCompliance Officers
  • Parent organisationABCB1C1B2
  • AA
  • BBB1B2
  • CCC1
CO of B sees B, B1 and B2
5

Reports

Report on every association

Reports cover all the organisations a user is associated with, so each branch and the parent office work from the same records.

  • Active and disabled organisations
  • Compliance Officers and Auditors see all
  • Activity reports overnight
Activity Report
Parent organisation
  • A
  • B
    • B1
    • B2
  • C
    • C1
  • Parent organisation
    Compliance Officers and Auditors see all
  • A, B, C
    Active and disabled organisations
  • B1, C1, B2
    Activity reports overnight

Access Rights

Access Rights, the fine tuning

Below the role, 18 named Access Rights switch features on or off for each account. What the list shows depends on the role selected.

Mei Lin

Standard User

Access Rights

Scanning

  • Single Scan
  • Batch Scan
  • Corporates

Results and due diligence

  • Scan Results
  • Batch Scan Results
  • Due Diligence Decisions
  • Due Diligence Report
  • Activity Report
  • Dashboard

Documents

  • View Supporting Document
  • Add Supporting Document
  • Manage Supporting Document
  • Delete Supporting Document

Administration

  • Organisation Management
  • Data Management

Services

  • Monitoring
  • ID Verification Service
  • Know Your Business Service

The decision, not the history

Due Diligence Decisions shows the final match decision, but not the history of decisions and comments behind it.

Rights that appear with the service

The ID Verification and Know Your Business rights show up only when the organisation has that service activated.

Corporates opens the corporate scans

Corporates works in addition to the single and batch scan rights to open corporate scans and results.

Secure by design

Secure sign-in and clear records

Team access is an account question, and the work behind it is on the record: who signed in, who ran the scan, who decided.

Enterprise single sign-on

Corporate logins work through OpenID Connect (OIDC) and SAML, configured together with the MemberCheck team via your Account Manager or Support.

  • OpenID Connect and SAML
  • Configured with MemberCheck

Password plus security question

Each account signs in with a password and a security question and answer, set at activation. Multiple failed attempts lock the account.

  • Chosen by the user at activation
  • Lockout after failed attempts

Account statuses

Every user sits in one of four states, and Compliance Officers manage them from Administration > Users.

Pending

Waiting for the user to set a password and security question to activate.

Active

Signed up and working. Web access is available.

Inactive

Deactivated, with no access.

Locked

Locked after multiple failed sign-in attempts.

One active API key per user

All accounts can use the API. A user generates their own key in My Profile, and only one key is active at any one time. MemberCheck recommends a dedicated service account for integrations, so access survives anyone leaving.

  • Generate, then Update
  • One key active at a time
  • Service account recommended

What the platform keeps

The records that show the team's work to a regulator.

  • Activity Report

    The overnight summary of each day's scanning, covering PEP and Sanctions, ID Verification and KYB.

  • Decision history

    Due diligence decisions and the comments recorded against scan matches.

  • Override History

    ID Verification overrides require a comment and keep the original outcome and evidence.

  • Last Login

    Each user's most recent sign-in, shown on the MemberCheck banner.

FAQ

Frequently asked questions

Answers about MemberCheck user access, roles and team structure.

How many users can a MemberCheck account have?

An unlimited number in every role except Compliance Officer, which is capped at 3 per organisation or suborganisation. Inactive Compliance Officers are not counted toward the 3.

What roles are there?

Six, from highest to lowest access: Compliance Officer, Advanced User, Standard User, Billing Officer, Data Entry Operator and Auditor. The Feature Permission Matrix sets what each one can do.

Can one person work across several departments or branches?

Yes. An account can be assigned to one or multiple organisations and suborganisations and keeps the same role across them. Different roles need separate accounts with their own unique usernames and emails.

How does someone join the platform?

The organisation's Compliance Officer creates the account, and the onboarding email carries the login and region details. The new user activates by setting a password and security question, and Pending becomes Active.

Can we fine tune access beyond the standard roles?

Yes. 18 named Access Rights refine each account, and they depend on the role selected, so what you see on the rights list changes with the role.

Does MemberCheck work with our corporate logins?

Enterprise single sign-on is available with OpenID Connect and SAML, configured with the MemberCheck team through your Account Manager or Support.

What happens to logins and API keys when someone leaves?

The account is deactivated, only one API key per user is active, and a dedicated service account keeps integrations running through staff changes. Accounts with no scan history can be deleted, and deleted accounts cannot be restored.

Bring your whole team onto one platform

See how MemberCheck Unlimited User Access fits your structure, roles and branches.