Warehouse Software User Roles and Permissions: A Guide

Good warehouse software gives every user a personal login and only the access their job needs: manager, supervisor, operator or a read-only auditor. When the whole team shares one admin account, no transaction has an owner, and every stock discrepancy turns into a round of “it wasn’t me”.

Plenty of small and mid-sized warehouses go live with a single username and a password on a sticky note next to the monitor. It feels efficient at first. Then the first serious shortage appears, and the system cannot say who posted the issue note that caused it. This article explains the typical user roles in warehouse management software, why restricting each operator to their own warehouse matters, where an auditor fits, how Avadar handles roles and user limits per plan, and how to design your permission scheme on paper before go-live.

Why one shared admin login causes problems

Picture a hypothetical distribution centre with three storekeepers and a shift lead, all signing in as “admin”. On Monday morning a popular SKU shows twelve more units in the system than on the shelf. Each storekeeper says they did not touch it. The shift lead cannot find out who posted last week’s adjustment, because every entry carries the same user name. Hours of argument follow, trust takes a hit and nobody learns anything.

A shared account creates three recurring problems:

• Accountability disappears. If nobody can be identified as the person who posted a document, nobody has a personal reason to get it right.
• Costly mistakes get easy. A new hire who should only book receipts can also delete items or overwrite quantities.
• Staff turnover becomes a risk. When one person leaves, everyone’s password should change, and in practice it rarely does.

Personal logins also protect your staff. A storekeeper who works carefully can point to their own transaction history and show the discrepancy did not come from them. Missing access control is also one of the patterns in our article on common warehouse management mistakes.

Warehouse user roles: storekeeper, supervisor, manager and auditor

Role names vary between companies, but the division of work is remarkably similar. Avadar has four roles: manager, supervisor, operator and auditor. The table below is a general view of what each role typically does and what it is safer for that role not to do:

The principle behind the table is least privilege: everyone gets the smallest set of permissions without which their job would stall. Never grant extra access “just in case”; if it is needed one day, the manager can add it that day.

Restricting each operator to their own warehouse

Once a company runs several stores, say raw materials, finished goods and spare parts, the most damaging error is an operator posting into the wrong warehouse. Often it is not deliberate; the wrong entry was picked from a dropdown. Avadar limits each operator’s view to their own warehouse, so the wrong option simply is not on their screen.

In multi-branch networks this matters even more. In Avadar the separation between branches and warehouses is real, not cosmetic. In the Cargo (Barnama) edition for transport and logistics companies, each branch and operator sees and moves only the shipments of their own warehouse, and unlimited branches with full separation come with the Elite plan; see the Avadar Cargo edition. For other aspects of running several sites, read our guide to multi-warehouse management.

The read-only auditor role

An internal auditor, a finance manager or an external auditor needs to see warehouse records but should not be able to change a figure, even by accident. Handing them a manager account adds risk and weakens the review itself, because you can no longer say the reviewer had no hand in the data.

In Avadar the read-only auditor role, along with detailed rights for each user, starts at the Pro plan. A common use: after each round of cycle counting, the auditor goes through the adjustment entries and checks each reason with the supervisor, without anyone worrying about accidental edits.

Managing warehouse users in Avadar: limits per plan

Before choosing a plan, list everyone who will log in, not just storekeepers but shift leads, purchasing staff and the auditor. Then compare:

For trading and distribution businesses, the Trade edition on the Elite plan can switch on a multi-step approval flow where you decide which role approves which step. Roles then shape not only who can see and post, but also how goods-out requests get approved.

No default passwords, and a record of every change

Two details matter more than they look. First, no Avadar edition is delivered with a default password, so there is never a well-known login that half the building can guess. Second, every change in the system is logged. Combined with personal accounts, that history becomes meaningful: you can see which document was posted or corrected, when, and by whom.

On top of that, the receiving person signs the delivery slip on goods in, goods out and transfers (all plans), which extends the chain of responsibility to the moment goods physically change hands.

Checklist: designing roles before go-live

This is general advice that applies to any warehouse system:

1. List people and tasks. For each person, write down which documents they post in a typical week and which reports they need.
2. Separate sensitive duties. The person who receives goods should ideally not be the one who adjusts and approves stock differences.
3. Keep the manager role small. One or two people are enough; senior staff can be supervisors or auditors.
4. One person, one account. No shared login for the night shift or temporary workers; create a separate account and deactivate it when the assignment ends.
5. Keep passwords off paper and shared devices. If a warehouse phone is passed around, each person signs in and out with their own account.
6. Write an offboarding step. The day someone leaves, their account is disabled the same day.
7. Review permissions every few months. Job changes and moves between warehouses should show up in access rights too.

If your users and current stock live in Excel or older software, the P-Soft team migrates previous data into the new product; the contract and plan determine exactly what is included.

Frequently Asked Questions

Which user roles does Avadar have?

Manager, supervisor, operator and a read-only auditor. Pro and Elite add the auditor role and detailed rights per user.

Can an operator be limited to one warehouse?

Yes. Each Avadar operator works only in their assigned warehouse, and in the Cargo edition each branch and operator handles only their own shipments.

How many users does each plan include?

Start: up to 5 users and one warehouse. Pro: up to 20 users and up to 5 warehouses. Elite: unlimited users and warehouses.

Can we tell who made a wrong correction?

Every change in Avadar is logged. As long as each person uses their own account, you can see who made which change and when.

Why not give the auditor a manager account?

A reviewer should see, not edit. A read-only role removes the risk of accidental changes and makes the review more credible.

Want to map roles to your own team? See Avadar and request a demo.

Further reading

• What Is Warehouse Management Software & Why Every Business Needs It
• The Best Warehouse Management Software for Your Business: A Guide to Choosing and Comparing (2026)
• What Is Stocktaking? A Complete Practical Guide

Complete guide: warehouse management software