Roles and permissions reference
You will know what a Role does, which roles are confirmed to exist, and the questions to settle with support before you rely on a role to hide a screen.
Every user on the Users screen has one Role. The role decides which menus and actions the person sees after login. This page sets out exactly what is known about roles from the app and marks clearly what still needs confirming for your company, so that you do not assume a restriction that is not there.
What Is Confirmed
- The Users list has a Role column and the Add form has a Role dropdown; a role is required for every user.
- A Customer role exists. It is meant for customers who log in to see their own side of the business.
- Access is switched on and off per user with Is Active, independent of the role.
- Passwords are set and reset by an administrator with the key action on the Users list.
- Drivers do not use a Role. They log in to the mobile app with an OTP and are controlled by Enable Mobile App on the driver record and Enable Driver Mobile App under Settings › Company.
What Is Not Yet Confirmed
The following were not visible on the screens walked. Treat each as "where available" until you have checked it on your own company or asked support.
Question | Why it matters | How to check |
|---|---|---|
The full list of roles besides Customer (for example an owner, accountant or dispatcher role) | Decides whether you can separate billing staff from booking staff | Open Users › Add and read the Role dropdown |
Whether roles can be created or edited by you, or only by support | Decides whether a new job title needs a support request | Look for an add or edit control next to the Role list; if none, ask support |
Whether permissions are set per module (for example Payroll hidden from dispatchers) | Decides how much sensitive data a role exposes | Log in as a test user with the role and walk the menu |
What a Customer-role user sees: bookings, invoices, payments, PODs | Decides whether you can give customers self-service | Create a test Customer user linked to a test customer and log in |
Recommended Practice
- Give every person their own login so Created by and Approved by on bookings and vouchers mean something.
- Before giving a role to a customer or a junior user, log in once with a test user of that role and confirm what it shows.
- Switch Is Active off the day someone leaves. Do not reuse their login for the replacement; add a new user.
- Keep the number of users who can reach Settings and Users small; those tabs change numbering, taxes and the financial year for everyone.
Need Help?
Chat with the NShine ERP support team on WhatsApp at +91 79950 87755, or ask from inside the app. Last checked 9 November 2026 against app.nshineerp.com.