How Are Role Permissions in NocoBase Stronger Than in AppSheet? Boss, Accountant, Warehouse — Each Person Sees a Different System
by BAMFLOW • • 5 min read • Updated 9 Nov 2026
Role permissions in NocoBase explained: three levels of access, a cost-price field example, a sample matrix for four roles, and the mistake to avoid.
How Are Role Permissions in NocoBase Stronger Than in AppSheet? Boss, Accountant, Warehouse — Each Person Sees a Different System
Quick summary: NocoBase role permissions work on three levels: which pages a role can open, which actions it can perform, and which rows and fields it can see. Each role sees only its own part — cost prices, receivables and salaries stay hidden.
Imagine sales, warehouse, accounting and you all opening the same system. If everyone sees everything, sales sees cost prices, warehouse sees unrelated debts, a new hire sees the delete button. The answer is not trust, but design: each person sees, and can do, only what their responsibility requires. That is role-based permission — where NocoBase goes deeper than AppSheet. New here? Start with What is NocoBase?.
1. Three levels of NocoBase role permissions: pages, actions, and data by row and field
Level one: pages and menus. Director sees dashboards; accounting, receipts and receivables; warehouse, goods issues and stock; sales, customers and orders. A page a role cannot access is absent from its menu.
Level two: actions. Reaching a page does not mean doing everything on it: warehouse staff create goods issue notes, the lead approves them, nobody there deletes an approved note.
Level three: data, by row and by field. By row: each person sees only records in their scope — a rep sees their own customers, Da Nang warehouse not Hanoi stock. By field: within one record, some fields are hidden entirely.
To be fair to AppSheet: it offers basic access control — who can use which app, which tables are editable or read-only, per-user filters. For a small app that may be enough. NocoBase goes deeper: permissions managed centrally by role, across pages, actions, rows and fields, on every interface on the same data model — see one data table, five interfaces.
2. Cost price: a field only accounting and the director can see
Cost price is among the most sensitive numbers in trading: from it, anyone can work out every order's margin, and if sales knows it, price discipline erodes.
An order table holds everyday fields — customer, quantity, selling price — and restricted ones: cost, gross profit, commission. With field-level permissions, cost and profit show only to Director and Accounting; for Sales and Warehouse they are absent, not masked. Sales still creates orders, warehouse still sees quantities to pick.
3. Sample setup: Director, Accounting, Warehouse and Sales
One user can hold several roles; permissions combine. Sample matrix:
| Data / Action | Director | Accounting | Warehouse | Sales |
|---|---|---|---|---|
| Dashboard | All | Finance | — | Own sales |
| Customers | All | View all | — | Own only |
| Orders | All | View all | To ship | Create/edit own |
| Cost, profit | View | View | — | — |
| Goods in/out | All | View all | Create/edit own | — |
| Stock | All branches | View all | Own warehouse | View only |
| Payments, debts | All | Create/approve | — | Own customers |
| Salaries | All | Payroll | — | — |
| Delete approved vouchers | Only director | No | No | No |
| Settings, permissions | Edit | No | No | No |
Start from minimum access: grant nothing by default, open rights as work requires. Define intermediate roles — warehouse lead, sales manager — with row-level access to their team's data, not director rights.
4. Test with real accounts before staff use the system
Configured does not mean correct. The gap between "I think it is locked" and "it is locked" only shows when you sign in as each role.
Create one test account per role — never test as admin, which sees everything. Check sensitive cases: as Sales, can you find cost price anywhere — list, form, export? As Warehouse, can you open receivables or see another branch's stock? A field hidden on the form but present in an export is not hidden. Re-run checks when you add a table, field or page.
5. The most dangerous mistake: granting rights to people, not roles
This mistake causes no incident at first. Someone urgently needs one extra right, so an admin grants it to that account "just this once". A year later, dozens of forgotten exceptions remain.
Granting by role fixes the root cause: people come and go, positions stay. A new rep given the Sales role gets exactly its rights; moving to sales from warehouse means swapping roles, and old rights disappear. Exceptions need an expiry date.
Conclusion
Permissions protect cost prices, debts, salaries and customer data. Because NocoBase covers all three levels centrally by role, one system can safely serve boss, accounting, warehouse and sales.
About BAMFLOW — BAMFLOW is the official NocoBase partner in Vietnam, implementing and training AppSheet, NocoBase and AI (300+ applications, 150+ customers, 1000+ learners).
- Want to build your own system? Register for the NocoBase AI Builder course (12 sessions) — build a real system on your own data, including permission design.
- Want BAMFLOW to design your permission matrix and implement your system? Message BAMFLOW via bamflow.vn.