Short answer: Draw the permission table before building the screens. For an internal tool, the important question is whether each person can access only the records and actions they need. A hidden button does not prove that the underlying data is protected.
Contents — jump to a section
A concrete example
Build a fictional expense-request tool with Employee, Manager and Finance roles. An employee submits their own request; a manager reviews their team's requests; Finance records payment. Keep the amount requested separate from the amount paid so approval does not silently become payment.
This is a suggested exercise, not a recorded product test. It describes the result to aim for; it does not claim that every listed tool can complete every step.
Prepare these inputs
List the records, their owners and the allowed actions. A starting table needs role, record scope, read, create, edit, approve and pay. Add two employees in different teams and sample requests with invented amounts.
Visit Bubble ↗Build it in this order
- Write one permission rule per action, including who may change a request after submission.
- Create the smallest request form and list view. Keep approval and payment as separate actions.
- Sign in as each sample user and try both the permitted action and another person's record URL.
Check the result
- Employee A cannot read or edit Employee B's request by changing a URL.
- A manager cannot approve a request outside their assigned scope.
- A paid request retains its approval history and cannot accidentally return to unpaid.
If the result fails
If a direct link exposes a record, stop using real data and fix the record-access rule. Removing the link from the menu is not a repair. If an approval changes the wrong field, split that action into a clearly named transition.
Visit Softr ↗Time and cost to watch
Include the work of maintaining team membership, handling corrections and reviewing permission changes. A visually simple tool can become expensive if each new team needs a separate copy.
Tools worth comparing
Compare Bubble, Softr, Glide and Jotform against this permission table. Confirm the exact access controls and plan requirements for your chosen design. A form-only process may be enough when there is no need for a persistent staff portal.
Sources and scope
The product references for this guide were last checked on 13 August 2026; details may have changed since. Check the official pages below for current plans, limits and terms before choosing a service.