User Management Overview

What is User Management?

User Management is Sumo Ledger’s access-control module for defining roles, users, and user types. It controls who can sign in, what features they can access, and how users are categorized across the platform.

User Management sits under Configurations → System Settings and consists of two primary areas:

Area	Purpose
Roles	Define permission sets by assigning system features to named roles
Users	Create user accounts and assign roles and user types

A related setting — User Types under Accounting Settings — provides an additional classification layer used when assigning users and configuring business rules.

---

User Management Capabilities

Capability	Description
Role-based access control	Create roles and map them to system features (for example, DASHBOARD, CONF_PRODUCT, EXEC_JV).
User account management	Add users with username, password, and an initial role assignment.
Role assignment	Assign or change roles for existing users through the Assign Role dialog.
User type assignment	Classify users with types such as admin through Assign User Type.
Feature granularity	Control access at the module level — configuration screens, reports, transactions, and logs.
Bulk permission setup	Use Create All Permission to initialize the full feature set for a role.
Load configuration in memory	Publish role and user changes to the running service.

---

Navigation

User Management lives inside the Configurations module.

1. Click Configurations in the main sidebar.
2. Under System Settings, select Roles or Users.

Section	URL	Purpose
Roles	/settings/role/list	Manage roles and feature permissions
Users	/settings/auth-user/list	Manage user accounts and assignments

Related setting:

Section	Location	Purpose
User Types	Configurations → Accounting Settings → User Types	Define user type categories used in assignments

---

How Roles, Users, and Features Connect

┌──────────────────────────────────────────┐
│ Administrator creates a Role             │
│ (for example, RM, Sumo User Guide)       │
└──────────────────────────────────────────┘
                    │
                    ▼
┌──────────────────────────────────────────┐
│ Features assigned to the Role            │
│ (Set Feature or Create All Permission)   │
└──────────────────────────────────────────┘
                    │
                    ▼
┌──────────────────────────────────────────┐
│ User account created (+ Add User)        │
└──────────────────────────────────────────┘
                    │
                    ▼
┌──────────────────────────────────────────┐
│ Role assigned to the User                │
│ (at creation or via Assign Role)         │
└──────────────────────────────────────────┘
                    │
                    ▼
┌──────────────────────────────────────────┐
│ User Type assigned (optional)            │
│ (via Assign User Type)                   │
└──────────────────────────────────────────┘
                    │
                    ▼
┌──────────────────────────────────────────┐
│ User signs in with role-based access     │
└──────────────────────────────────────────┘

1. An administrator creates a Role and assigns Features that define what the role can access.
2. A User account is created with a username, password, and role.
3. Optionally, a User Type is assigned for additional classification.
4. When the user signs in, the system enforces permissions based on their assigned role’s features.

---

Typical Roles

Role	Description	Example Features
ADMIN	Full administrative access	All features (typically unrestricted)
USER	Standard user for viewing reports	Report-oriented access
API_USER	Service or integration account	AUTH_SERVICE
RM	Relationship Manager	AUTH_SERVICE, DASHBOARD, TASKS
BM	Branch Manager	TASKS
Sumo User Guide	Demo/training role with broad access	Configuration, transactions, reports, and logs

---

Related Modules

Module	Relationship
Form Builder	Maker, Checker, and Approver roles on forms map to user types or roles.
Process Configuration	Process execution visibility depends on user permissions.
Product Configuration	Requires CONF_PRODUCT feature for access.
COA Mapping	Requires CONF_COA_MAPPING feature for access.

---