Microfinance Software

User Roles and Access Control for Microfinance Software

Give branch staff, collection agents and the cashier only the screens and actions they need. Rules are enforced by the server, not just hidden on screen.

Last updated 14 November 2026 · CK Tech Solutions, Anna Nagar, Chennai

Short answer: In CK Tech microfinance software every screen has its own privileges for each role: view, create, edit and delete. The server checks them on every save and delete, and the screen hides the buttons a role cannot use. The admin role has full access. A user who is the collection agent of a group sees and collects only the groups assigned to them. Settlement, users, roles and MIS reports need the view right even to read.

At a glance

User Roles and Access at a glance
Privileges	View, create, edit and delete, set per screen for each role
Enforced by	The server on every save and delete; buttons are also hidden for the role
Admin role	Full access
Collection agents	See and collect only the groups assigned to them, with a "Today's groups" filter
Sensitive screens	Settlement, users, roles and MIS reports need the view right to open
Sign-in	Login is limited to 10 failed attempts per user

How do roles and privileges work?

A role is a named set of screen privileges. You create the roles your office needs and assign each user one of them.

Roles

Create roles such as branch manager, cashier or collection agent.

Per-screen privileges

Choose view, create, edit and delete for each menu screen.

Server-side checks

A saved or deleted record is checked against the role, so a hidden button is not the only protection.

Hidden buttons

Create, edit and delete buttons and grid actions disappear for roles without the right.

How are collection agents limited?

Field agents should see their own groups, not the whole portfolio.

Own groups only

A user who is the collection agent of a group sees and collects only those groups.

Today's groups

The collection screen can show only the groups whose collection day is today.

Who collected

The collecting user is taken from the login, not typed in.

Who changed what

Most records store who created and last changed them, and when.

How it works

Create the roles your office needs.
Set view, create, edit and delete for each screen on each role.
Create users and assign a role to each.
Assign each collection agent to their groups.
Staff sign in and see only what their role allows.

Frequently asked questions

Not yet. Branch is stored on groups and loans, but non-admin users are not limited by branch today. Collection agents are limited by group. Branch-wise access can be discussed as custom work.

Both. The server rejects a save or delete that the role is not allowed to do, and the screen hides the matching buttons.

No. A collection agent sees and collects only the groups assigned to them.

Most records keep who created and last changed them and when. A full change history for every field is not included.

Login is limited to 10 failed attempts per user.

See it with your own data

Tell us how you lend and collect, and we will show you this on a live demo. Free 2-month trial.

Request a demo