Managing Roles
This guide covers administrator tasks on the Roles page: creating roles, assigning features, and initializing permissions.
Opening the Roles List
- Click Configurations in the main sidebar.
- Under System Settings, click Roles.
- The roles list opens at
/settings/role/list.
Each row displays:
| Column | Description |
|---|---|
| Role Id | Unique system identifier (for example, 01KJVH1KR79M8P1SVB2CBDN86R) |
| Name | Role display name (for example, ADMIN, RM, Sumo User Guide) |
| Features | Comma-separated list of features assigned to the role |
| Description | Brief explanation of the role's purpose |
Creating a Role
- On the Roles page, click + Add.
- The Add Role dialog opens.
- Fill in the fields:
| Field | Description |
|---|---|
| Role Name | Unique name for the role (for example, Sumo User Guide). Use uppercase or descriptive names consistent with your organization. |
| Description | Optional text describing the role's purpose (for example, For Sumo User Guide). |
- Click Add.
- The new role appears in the roles table.
After creating a role, assign features using Set Feature or Create All Permission (see below).
Assigning Features to a Role
Features control which modules and actions a role can access. Use Set Feature to assign specific permissions.
Configuration Procedure
- On the Roles page, click Set Feature.
- The Set Feature dialog opens.
- Select a Role Name from the dropdown (for example,
Sumo User Guide). - Under Feature, select one or more features from the checklist.
- Click Set Feature.
- Verify the selected features appear in the Features column for that role.
Feature Categories
Features fall into several groups:
Configuration features (CONF_*)
| Feature | Grants Access To |
|---|---|
CONF_PRODUCT | Product Configuration |
CONF_COA_MAPPING | COA Mapping |
CONF_TARIFF | Tariff Configuration |
CONF_PROCESS | Process Configuration |
CONF_TABLE | Table Configuration |
CONF_FEED | Feed Configuration |
CONF_CONTRACT | Contract Type Configuration |
CONF_TXN_CONTROL | Transaction Controls |
CONF_ASSETS | Asset Groups |
CONF_CHANNELS | Channel Types |
CONF_USERS | User Management |
CONF_RG | Reporting Groups |
CONF_JOBS | Jobs Configuration |
Operational features
| Feature | Grants Access To |
|---|---|
DASHBOARD | Home dashboard |
TASKS | Tasks module |
PROCESS_TXNS | Transaction processors |
EXEC_JV | Journal voucher posting |
PRODUCT_ACCOUNTS | Product accounts |
CONNECT | Connect integrations |
TABLE | Table (operations) |
FEED | Feed (operations) |
TARIFF | Tariff (operations) |
CONTRACT | Contracts |
JOBS | Jobs |
Reporting features
| Feature | Grants Access To |
|---|---|
TRIALBALANCE | Trial Balance report |
TXN_REPORT | Postings / transaction report |
System features
| Feature | Grants Access To |
|---|---|
AUTH_SERVICE | Authentication and API access |
LOAD_CONF | Load Configuration In Memory |
LOGS | System logs |
Important Notes
- Assign only the features required for each role — avoid granting unnecessary configuration access.
- Configuration features (
CONF_*) control access to the Configurations subsections. - Operational features control access to day-to-day ledger functions in the main sidebar.
Create All Permission
Create All Permission initializes the complete set of system features for a role. Use this when setting up a demo, training, or full-access role.
Configuration Procedure
- On the Roles page, click Create All Permission.
- A success notification confirms creation (for example, Created All Permissions).
- Verify the role's Features column shows the full feature list.
Example: The Sumo User Guide role after Create All Permission includes features such as TASKS, CONF_FEED, CONF_COA_MAPPING, CONF_TARIFF, TRIALBALANCE, EXEC_JV, DASHBOARD, PRODUCT_ACCOUNTS, LOGS, and AUTH_SERVICE.
Important Notes
- Use Create All Permission only for roles that genuinely require full system access.
- Review the resulting feature list before assigning the role to production users.
- Prefer Set Feature for roles with limited, specific access needs.
Example Role Configurations
| Role | Features | Description |
|---|---|---|
| ADMIN | (unrestricted) | Full administrative access |
| USER | — | Normal user for viewing reports |
| API_USER | AUTH_SERVICE | API and service integration account |
| RM | AUTH_SERVICE, DASHBOARD, TASKS | Relationship Manager |
| BM | TASKS | Branch Manager |
| Sumo User Guide | All features | Demo and training role |
Load Configuration In Memory
After creating or updating roles, publish changes to the running service:
- Click Load Configuration In Memory in the top-right corner.
- Confirm the action if prompted.
Important Notes
- Role changes may not take effect until configuration is loaded into memory.
- Coordinate with your team before reloading configuration in production.
Configuration Checklist
Before assigning a role to users:
- Role name is unique and follows naming conventions.
- Description explains the role's purpose.
- Required features are assigned via Set Feature or Create All Permission.
- Feature set has been reviewed — no unnecessary configuration access granted.
- Configuration has been loaded into memory if required.
- A test user with the role can access expected modules and is blocked from unauthorized areas.