User Roles and Permissions: Who Can See and Change What?
Plan permissions from the business side first: list who uses the system, what each group needs to see and do for their job, and give nothing more. Then make sure the software enforces those rules on the server for every page, request, file and export, records who changed what, and is reviewed whenever people join, leave or change jobs. This deserves real attention: broken access control holds the number one position in the OWASP Top 10:2025, the best-known list of serious security risks in web applications.
Why permissions matter more than they seem
OWASP reports that 100% of the applications tested for its 2025 list had some form of broken access control. When access control fails, people can see information they should not, change or delete data, or perform business functions outside their limits. In a business system that might mean a sales assistant exporting the whole customer database, a customer opening someone else's invoice, or a temporary worker changing prices.
Permissions are also part of data protection law. Article 25 of the GDPR requires that, by default, only the personal data necessary for each specific purpose is processed, and says this applies to the amount of data collected, the extent of processing, the storage period and its accessibility. Article 32 adds that anyone acting under the organisation's authority who has access to personal data should process it only on instructions. Clear roles are the practical way to meet both.
Start with people and tasks, not with the software
- List the groups of users: owners or management, sales, warehouse, accounting, support – and external users such as customers, partners or subcontractors. Integrations count too: an API key used by your accounting software is a user with permissions.
- List the data: customers, orders, sale prices, purchase prices and margins, invoices, employee data, documents.
- List the actions: view, create, edit, delete, export, approve.
- Fill in a matrix of who may do what, and ask the people who do the work whether it matches reality.
An example for a small trading company – yours will differ:
| Sales | Warehouse | Accounting | Manager | |
|---|---|---|---|---|
| Customer contacts | View and edit own customers | Delivery address only | View | Full |
| Orders | Create; edit until confirmed | View; change shipping status | View | Full |
| Purchase prices and margins | No | No | View | View and edit |
| Invoices | View for own customers | No | Create and edit | View |
| Exporting the customer list | No | No | No | Yes |
| Managing users | No | No | No | Yes |
Roles, plus a few rules
The classic approach is role-based access control. NIST describes it simply: each user is assigned one or more roles, each role is assigned privileges, and security is managed at a level that corresponds to the organisation's structure instead of user by user – which reduces the cost of administration. For most small and mid-sized businesses, a handful of roles is the right starting point.
Roles alone rarely describe real life, though. Typical extra rules are:
- Ownership – a sales rep sees their own customers, not everyone's;
- Location – staff see the data of their own office or warehouse;
- Status – an order cannot be edited once it has been invoiced;
- Limits – a discount above a certain level needs a manager's approval.
OWASP's Authorization Cheat Sheet goes further and says that attribute- or relationship-based access control should typically be preferred over pure role-based control in application development, partly because role-only systems drift towards "role explosion" as every exception becomes a new role. In practice, a few roles combined with a few clear rules is usually easier to understand and maintain than dozens of roles.
Where money is involved, also separate duties: the person who adds a new supplier should not be the same person who approves payments to that supplier.
Technical principles to insist on
- Least privilege and deny by default. OWASP recommends granting each role only the minimum access it needs and configuring applications to deny access unless it is explicitly allowed.
- Check on the server, on every request. Hiding a button is not protection. OWASP is blunt that developers must never rely on client-side access control checks; attackers modify URLs, page data and API requests to get around controls.
- Check the specific record. A common failure is letting a user open someone else's order by changing a number in the address. The OWASP API Security Top 10 (2023) puts this problem, "Broken Object Level Authorization", in first place.
- Protect fields, not only screens. If purchase prices are hidden on screen but included in the data the API sends to the browser, they are not hidden. OWASP lists this as "Broken Object Property Level Authorization".
- Protect files and exports. PDF invoices, uploaded documents and spreadsheet exports must follow the same rules as the screens. OWASP specifically recommends including static resources in access control policies.
- Log access and changes. Record who did what and when, log failed access attempts and alert someone when they pile up.
- Test permissions with automated tests, not only by clicking around before launch.
Everyday administration
- Personal accounts only. Shared logins make the audit log meaningless.
- Joiners and leavers. Remove access the day someone leaves; change their role the day their job changes.
- Regular reviews. OWASP advises periodically reviewing permissions for "privilege creep" – people collecting access over the years that they no longer need.
- Few administrators, with stronger protection for their accounts, such as two-factor login.
- Role management without a developer. If adding a user or changing a role needs a programmer, people will start sharing accounts instead.
Customer-facing systems need the same care; see what to include in the first release of a customer portal. If you are choosing between an off-the-shelf system and your own, custom CRM vs existing CRM can help with that decision.
Questions to ask your developer or vendor
- Are permissions checked on the server for every page, API request, file and export?
- Can a user open another customer's record by changing an ID in the address or the request?
- Can we create users and change roles ourselves?
- Can we restrict individual fields, such as purchase prices?
- Is there an audit log, what does it record and how long is it kept?
- How are customer and partner accounts separated from staff accounts?
- How are permissions tested when the software changes?
Getting roles right is much easier at the design stage than after launch. If you are planning a CRM, admin panel or customer portal, we can help you map who needs to see and change what, and build those rules into the software as part of our web-based software development. Get in touch to discuss your system.
Sources
- A01 Broken Access Control – OWASP Top 10:2025
- Authorization Cheat Sheet – OWASP
- OWASP Top 10 API Security Risks – 2023 – OWASP
- Role Based Access Control – NIST Computer Security Resource Center
- Art. 25 GDPR – Data protection by design and by default – gdpr-info.eu
- Art. 32 GDPR – Security of processing – gdpr-info.eu