# Page: Roles and Permissions

## Purpose

This page explains how roles and permissions control what each user can do inside the fraud and AML application.

## Roles

A role defines the general responsibility of a user. Common examples include:

- analyst: reviews scores and cases;
- investigator: works through cases and updates status;
- administrator: manages users, roles, and configuration.

## Permissions

Permissions define what actions a user is allowed to perform. Examples include:

- view scores;
- open and update cases;
- edit rules or configuration;
- manage users and access rights.

## Example usage

Example: an analyst may be allowed to review case details but not change a rule definition. An administrator may be allowed to change configuration and manage accounts.

## Recommended approach

- assign the minimum required permissions for each role;
- review role access whenever responsibilities change;
- test access after making changes to ensure users can complete their intended tasks.

## Notes

Roles and permissions are critical for maintaining both security and operational control. They ensure users can work efficiently without having access to unrelated or risky functions.