Roles and permissions
A role is a set of permissions. How much data a role reaches is decided separately, each time you give it to somebody.
Before you start
- The
role.viewpermission to look,role.manageto change anything. The Owner and HR roles holdrole.manage. - What you may hand out depends on the role you hold. The Owner may give out any role. Everybody else may give out HR and Manager and nothing else — not Owner, not Payroll, and not a role your company invented. Otherwise the permission to assign roles is the permission to become anything, starting with Payroll and every salary behind it. The list on the screen only shows what you may give.
The four roles you start with
- Owner — everything. It cannot be edited or switched off, and a company always has at least one.
- HR — staff, attendance, shifts and requests. Deliberately not salaries:
payroll.view_salaryis a separate permission so that HR can run attendance without seeing what anybody earns. - Payroll — salaries and the attendance they are calculated from, and nothing about approvals or org structure.
- Manager — a web-admin role for a manager who also opens the admin. Being an approver is not a role: that comes from the org structure, and a team lead who only approves in Telegram needs no role at all.
`employee.view_sensitive` is a permission of its own, for the most personal part of a staff record: the ID document's type, number and expiry date, the NSSF number, the work permit and its expiry date, and the salary account, and the files attached to the record. Owner and HR hold it; Manager does not, so a team lead can read their team's records without their ID and account numbers. Like every permission it reaches only as far as the scope it was given with, so an HR role over one branch sees these fields for that branch alone. Changing the fields also takes employee.edit. MekongHRM never writes them to its logs or sends them with error reports.
Steps
Change what a role can do
- Open Roles and permissions.
- Tick or untick permissions in the matrix. A changed box is tinted until you press Save; Cancel puts every box back. Owner is always the first row and cannot be changed.
- To put a built-in role back the way it shipped, press its Restore defaults button.
Give somebody a role
- On the same screen, pick the person and the role. Anybody on the payroll can be picked,
including somebody who has not linked Telegram yet — the role waits for them and is theirs the moment they link, so you do not have to remember to come back.
- Pick the Data scope:
- Whole company — every branch and every department.
- One branch — one place of work.
- One department — one department and what sits under it.
- Their own reports — only the people who report to them.
- Write why in Reason, and press Assign a role.
The reason is kept in the activity log. Access questions are always asked months later, and this is where the answer lives.
What you should see
Somebody with several roles holds the union of their permissions, each over its own scope. An HR role over one branch and a Manager role over their own reports is a normal combination, not a conflict.
What the scope actually does
It decides which people somebody can see, and every screen that lists people follows it: the staff list, the attendance grid, the company leave balances, and every request. Owner and HR are normally company-wide, so they see everything. A Manager scoped to a department sees that department.
Four things worth knowing, because each of them surprises somebody:
- A department includes everything under it. Giving somebody a department
is not giving them the department minus its teams.
- Two roles add up. Somebody with one role over Production and another
over Sales sees both. Scopes are grants, not limits, so a second one never takes away what the first gave.
- Direct reports means the people whose manager is them. If the account
has no employee record of its own, that is nobody — not everybody.
- People always see their own row, whatever their scope says.
Somebody who approves for a team but does not manage it
Give them a role holding the request permissions, scoped to that unit, so they can see the team's requests. Then add them as an extra approver on the same unit under Approvals so they can decide them — see Setting up approvers.
They are two settings because they are two different things, and plenty of people need only the second: an approval card arrives in Telegram whether or not somebody ever opens the web admin.
When MekongNet support opens your company
If you report a problem, somebody at MekongNet may open your company to look at it — the attendance app, or the payroll app if you have it. They give a reason each time. While they are in, they have the same rights as your Owner, across the whole company, salaries, documents and bank accounts included: support that cannot see or fix what you are asking about cannot help. Every page they see carries a band saying they are in MekongNet support mode.
Anything they change is in your activity log under their own name, with a MekongNet mark; point at the mark, or open the line, to read the reason they gave when they opened your company. That is how you can see who at MekongNet changed what.
Reading the activity log
Activity log, under Settings, lists what was changed, newest first, fifty lines at a time; Load more at the bottom brings the next fifty. Each line says when it happened, on your company's clock, who did it, which group it belongs to, what was done, who or what it was done to, and the reason given. The lines sit under Today, Yesterday and the date.
- Narrow the list by dates, by who did it — System is the work the product does on its own — by group, or by searching the reasons and the names of the people the lines are about.
- A line with an arrow opens to show its details: the dates, the before and after of a change, the pay item. An amount of money is shown only to somebody who also holds
payroll.view_salary; everybody else sees the rest of the line. A salary change never shows the amount, only the date it took effect. - When the change was made to a person, their name opens their record, if you may see it.
- How far back the list goes depends on your plan, and the line under the title gives the date. Nothing older is deleted: a longer plan shows it again.
If something goes wrong
Owner holds everything and cannot be changed. — so that a company cannot trim away the only role able to put the permissions back.
A company must always have at least one Owner. — removing it would leave nobody who could give the role to anyone.
A branch scope is refused without a branch. A scope that names a branch has to say which one. Left empty it would quietly mean everything, which is the wrong way round for this to fail.
Somebody cannot see a menu item. A section nobody holds the permission for is hidden, not shown and refused. Check what their roles grant before assuming something is broken.
Last checked 02/10/2026