User Roles & Permissions
Give Every Role Exactly the Access It Needs
User roles and permissions decide who can do what and see what. iCargos controls access at the level of individual actions across 92 modules, and scopes the data each person sees to their own branch, franchise or customers — so a rider, a franchise manager and head office all work in the same system without ever stepping on each other.
Permissions down to the individual action
Access isn't just "on or off" per screen. For each of 92 modules, you grant a role only the actions it should have.
View
Add
Edit
Delete
Approve
Print
Import
Export
A Customer Service agent can view and comment on orders but not delete them; a finance user can print and export but not edit; a branch clerk can add bookings but not approve invoices. You set it once per role, in Users Permissions.
[ Screenshot: Users Permissions matrix ]Real product capture of the per-role permission grid (module × action) — awaiting capture from design.
Roles for how a courier actually runs
Start from roles that map to real jobs, then tune each one's permissions to your own structure.
Super Admin & Admin
Full run of the platform, including Users Permissions itself. Super Admin sits above the permission checks so head office is never locked out.
Branch & Franchise Manager
Run their own unit — a branch manager over their branch and its franchises, a franchise manager over their franchise alone.
BDM / BDE
Sales roles scoped to their own assigned customers, so a business developer sees the accounts they own and no one else's.
Customer Service
Handle orders, comments and merchant queries with the actions they need to help — without edit or delete rights they shouldn't have.
Rider
The field role: assigned pickups and deliveries, scan and status updates, and proof of delivery — nothing back-office.
Merchant
Your customers, each seeing only their own shipments, bookings, invoices and wallet — never another merchant's data.
Everyone sees only their slice of the data
Permissions decide what a role can do; scoping decides whose records they can do it to.
| Role | Sees |
|---|---|
| Super Admin / Admin | Everything across the business |
| Branch Manager | Their branch — and its child franchises |
| Franchise Manager | Their franchise only |
| BDM / BDE | Only their own assigned customers |
| Merchant | Only their own shipments |
Frequently asked questions
How granular are the permissions?
Very. For each of 92 modules you can grant a role any combination of eight actions — View, Add, Edit, Delete, Approve, Print, Import and Export — so a role gets exactly the rights it needs and nothing more. It's all set per role in Users Permissions.
Can a manager be limited to just their branch or franchise?
Yes. Data is scoped by role: a branch manager sees their branch and its child franchises, a franchise manager sees only their own franchise, and a BDM sees only their assigned customers — the same screens, safely narrowed to their slice of the data.
Do merchants see each other's shipments?
Never. Each merchant account is scoped to its own shipments, bookings, invoices and wallet only. One merchant can't see another's data.
Can I create roles for my own structure?
Yes. You start from roles that map to real courier jobs — admin, branch and franchise managers, sales, customer service, riders and merchants — and tune each role's module-by-module permissions to match how your business is organised.
Who can change permissions?
Access to Users Permissions is itself a permission, so only the roles you allow — typically Super Admin and Admin — can change what other roles can do. Super Admin sits above the checks so head office always retains control.
Lock down access without slowing anyone down
Book a demo and we'll set up a role, scope it to a branch, and show the permission model live.
We’re Here to Help
Need assistance? Reach out to us anytime.
iCargos © Copyright 2026. All Rights Reserved. - Powered By IT Vision Pvt. Ltd.