Per-person permissions
Give one person a little more, without redrawing a role.
Per-person permissions let you add a specific capability to one teammate on top of their role, so a single person can do a bit more without you having to create a new role for everyone like them.
A role gets most people most of the way. But there is always the one person who is the exception. The packer you trust to adjust stock during a count. The inventory manager you want to also see the orders list while a sale is on. With per-person permissions, you grant that exact capability to that one person, added on top of the role they already have, instead of cloning a role or loosening the role for everyone who shares it.
An override is a single permission picked from the same catalog your roles draw from: view orders, pack and ship, adjust stock, record receipts, edit products, and the rest. You tick the one box that person needs and save. It applies in addition to their role, so you are only ever adding, never quietly taking away what their role already grants. The change takes effect the next time they load the workspace.
This matters when your team is small and your exceptions are real. Across Meesho, Flipkart and Amazon work, the shapes of people's jobs rarely line up perfectly with three or four fixed roles. Overrides let you handle the edge cases one at a time, keep your role list short and meaningful, and avoid the trap of one giant role that can do everything because it was easier than being precise.
Built into per-person permissions
Grant one capability to one person
Add a single permission, like adjusting stock or viewing orders, to an individual teammate without touching the role they share with others.
Layered on top of the role
Overrides are additive. The person keeps everything their role grants and gains the extra permission you tick, so you never have to rebuild a role from scratch.
Picked from the same permission catalog
Choose from the same grouped list your roles use, covering orders, stock, products, receipts, team and wallet, so an override means exactly what it says elsewhere in managemate.
Per person, not per role
Adjusting one teammate's overrides changes only that teammate. Everyone else on the same role is unaffected, so a one-off stays a one-off.
Enforced on every action
Permissions are checked on the server for each action, not just hidden in the menu, so an override genuinely controls what a person can do, not only what they can see.
Reversible at any time
Untick the override and save to remove the extra capability. The person drops back to exactly what their role allows, with no leftover access.
From setup to everyday use
- 01
Open the person
Go to the users area of your workspace and open the teammate whose access you want to adjust. Their current role is already in place.
- 02
Tick the permission they need
Open their permission overrides and check the specific capability, such as adjusting stock, from the grouped catalog. You are adding on top of their role, not replacing it.
- 03
Save and it applies
Save the change. It takes effect the next time that person loads the workspace, and it affects only them, no one else on the same role.
In the day-to-day
For a trusted packer during a stock count
Your Pick and Packers normally cannot change stock levels, which keeps fulfilment focused during a busy shift. For a count, grant one reliable packer the adjust-stock permission so they can correct numbers as they go, then remove it when the count is done. Every other packer stays unchanged.
For an inventory manager covering orders
Your Inventory Manager keeps the catalog and stock straight but does not pack orders. During a heavy Meesho or Flipkart sale, add the pack-and-ship permission to that one person so they can pitch in on fulfilment, without making order packing part of the role for every inventory manager you hire later.
For a senior teammate who is almost an admin
Someone you trust needs to see the wallet ledger to reconcile order fees, but you are not ready to make them a full admin. Give them just the wallet view permission as an override, so they get the one thing they need and nothing more.
Per-person permissions, answered
How is a per-person permission different from a role?
A role is a named set of permissions you assign to many people. A per-person permission is a single capability added to one individual on top of their role, for when that one person is an exception to the role they share.
Does an override replace the person's role?
No. Overrides are added on top of the role. The person keeps everything their role grants and gains the extra permission you tick. To take access away, you would change their role rather than use an override.
Can I use overrides to remove a permission someone has from their role?
No. Overrides only add capabilities. If you need someone to have less than their role grants, move them to a more limited role, or adjust the role itself.
When does the change take effect?
The next time that person loads the workspace. There is no need for them to be invited again or to reset anything.
When should I create a new role instead of adding overrides?
Keep overrides for genuine one-offs. If you find yourself granting the same extra permission to several people, that is a sign the role should change or a new role is worth creating, so your access stays easy to reason about.
Do overrides actually stop someone from doing things, or just hide menus?
They stop the action. managemate checks permissions on the server for every action, so what someone can do is governed by their role plus overrides, not only by what appears in the menu.
Bring your marketplaces together
Tell us what you sell and where. We will set up your workspace and walk you through the first orders.