Decide who can do what, before the busy afternoon
Roles, limits and approvals set once and applied everywhere. A cashier sells, a manager discounts, finance approves, and every action carries the name of the person who took it.
- Unlimited staff accounts
- Limits enforced by rule
- Named audit trail
Included in every account · No per-user charge · Revoke access instantly
Shift closed
₦0 variance
Tolu A. · Ikeja counter
Controls that arrive as a conversation arrive too late
Asking a supervisor to decide whether this discount is allowed, in front of a customer, on a Saturday, is not a control. It is a negotiation, and it produces a different answer every time depending on who is standing there.
Decided in advance, not under pressure
Who can discount, refund, void a sale, approve a payment or see the margin, settled once as a rule. Nobody has to make that judgement at a busy counter with a customer waiting.
Everyone has their own login
Shared logins are the single fastest way to destroy an audit trail, and they exist mostly because software charges per user. Here staff accounts are free, so there is no reason to share one.
Every action carries a name
Sales, discounts, refunds, price changes, stock adjustments and approvals are all recorded against the person who made them, with a timestamp. Patterns become visible long before they become expensive.
Set up a new starter in about a minute
Add the person
Name, contact and which outlet they work at. They receive their own login rather than being handed a shared one.
Give them a role
Cashier, supervisor, store manager, finance or a role you define. The role carries the permissions, so a new starter is set up in seconds.
Set the limits
Discount ceilings, refund rights, approval thresholds and what they can see. Different by outlet where that makes sense.
Let the record do the rest
Every action is attributed automatically. Shift reports, cash variance and approvals all name the person involved.
The rules are only real if the system holds them
A written policy depends on everyone remembering it on a difficult day, and on a supervisor being willing to have the conversation. A permission enforced by the system removes the negotiation entirely, which is easier on the staff as well as the owner.
- Roles you define, applied per outlet
- Discount and refund ceilings enforced at the counter
- Approval thresholds that cannot be talked past
Staff
24 active
Ngozi A.
Finance
Tolu A.
Cashier, Ikeja
Emeka O.
Store manager
Every permission change is recorded against the person who made it
Attribution protects the honest majority
Most staff are not the problem, and the absence of a record hurts them most. When a till is short and nobody can say who was on it, suspicion spreads across everyone. A named trail settles the question quickly and quietly.
- Shift open and close, with counted cash and variance
- Every discount, refund and void named and timestamped
- Permission changes recorded against who made them
Permissions
By role
Action
Cashier
Manager
Finance
Give a discount
Refund a sale
Approve a payout
Edit a price
What changes when everyone has their own login
The usual way
- One login shared by everyone on the floor
- A discount policy that depends on who is asking
- Cash shortfalls with no way to say who was on the till
- Access still working weeks after someone has left
- Suspicion spread across a whole team by one incident
With Niimbu
- A named login for every person, at no extra cost
- Limits the system enforces, identically for everyone
- Variance attributed to a shift and a person
- Access revoked the same day, from anywhere
- A record that clears the people who did nothing wrong
What you can control
Roles you define
Start from sensible defaults and adjust, rather than building from nothing.
Per outlet access
Someone can manage one branch and only see their own.
Discount and refund limits
Ceilings enforced at the point of sale, not discovered in a report.
Approval thresholds
Payments above a figure need a second person, by rule.
What they can see
Hide cost prices, margins or company totals from roles that do not need them.
Shift management
Open with a float, close with a count, variance attributed to the shift.
Full audit trail
Every action timestamped, named and exportable.
Instant revocation
Remove access the moment someone leaves, from anywhere.
Unlimited staff accounts
No per-user charge, so nobody has a reason to share a login.
Charging per user is what makes businesses share logins.
And a shared login turns every other control into decoration. Staff accounts are free here because attribution is worth more to the business, and to the staff, than the licence fee would be to us.
Wherever more than one person touches the money
Retail and supermarkets
Cashiers, supervisors and managers with different rights at every till.
Restaurants and food
Voids and comps controlled by rule, with shift reports per server.
Multi-branch businesses
Branch managers who see their own outlet, and head office that sees all of them.
Pharmacies and clinics
Controlled items and dispensing recorded against the named person.
Hotels and hospitality
Access by department, with charges and settlements attributed correctly.
HR software
See how staff records connect to payroll and day to day operations.
Staff accounts are free, and always will be
Add everyone who works in the business, each with their own login and their own permissions. Niimbu is priced on money moving, so growing the team never changes the bill.
- Unlimited staff accounts
- Roles, limits and approvals included
- Free login for your accountant
Frequently asked questions
How many staff accounts can I create?
As many as you need, at no extra cost. This is deliberate. Charging per user pushes small businesses to share one login, which destroys attribution and makes every other control meaningless, so Niimbu is priced on money moving instead.
What can I control per role?
Selling, discounting, refunding, voiding, editing prices, adjusting stock, approving payments and what figures a person can see. Roles can also be scoped to an outlet, so a branch manager manages their branch and sees only that.
Can I stop staff seeing cost prices or total revenue?
Yes. Visibility is part of the role. A cashier can sell without seeing margin, and a branch manager can run their outlet without seeing company-wide figures. Access to information is a permission like any other.
How does this connect to payroll?
Staff records are shared. Someone added here is available to payroll with their salary, deductions and payment details, so you are not maintaining one list for access and another for paying people.
What happens when a staff member leaves?
Revoke their access and it stops immediately, everywhere, including the counter. Their history stays on the record, which is what you need for any question that comes up afterwards.
How is cash variance attributed?
A shift opens with a float and closes with a count. Niimbu compares what was counted against what the sales say should be there and records the difference against that shift and that person. A pattern becomes visible long before it becomes a large number.
Can two people approve the same payment?
Yes. Above a threshold you set, a payment can require two approvals from different people, and neither can approve their own request. This is the standard control for larger payments and it costs nothing to switch on.
Is there an audit trail?
Yes, covering every action rather than just logins: sales, discounts, refunds, price changes, stock adjustments, approvals and permission changes, each timestamped and named, and exportable for an auditor.
More from Manage
Your books, customers, inventory and staff share one set of records. Every tool here feeds the same ledger.
The simpler way to scale your business!
Start free and see it working today, or talk to us about pricing for teams and higher volumes.