Start here.
Start with the jobs people need to finish. For each kind of person, list the records they need and whether they may view, change, approve or share them. Define the limits, including whose records they can use. Agree who grants access, when it ends and how your supplier will check the rules.
- Being able to see information and being allowed to change it are separate decisions.
- A job title alone does not explain which customers, jobs or locations someone should have access to.
- Plan temporary cover, changing responsibilities and departures alongside the first set of accounts.
What does each person need to finish their job?
Imagine a business booking customer visits and sometimes assigning work to outside contractors. This is a fictional planning example. The office coordinates appointments, the contractor carries out an assigned visit, and the customer checks the agreed arrangements.
Follow one appointment through those people. The contractor may need the address, agreed work and a way to report completion. That does not automatically mean they need every customer’s history, the business’s full calendar or internal pricing notes.
Ask what each person needs to know and what they must be able to do. Discuss access by task rather than giving everyone a broad label such as “staff.” Someone covering reception may need different information from someone preparing the work, even if both are employees.
OWASP’s guidance on app access recommends giving people only what they need for their work. Use that principle as a starting point for the discussion, then make the boundaries specific enough for your supplier to build and check.
Which actions need different rules?
Reading a booking, changing its time and approving an exception are different actions. A person may need one without the others. Walk through them separately instead of asking only who can open the page.
For our example business, an office colleague might prepare a changed appointment while a manager decides whether to approve a special arrangement. The contractor might add completion notes without changing the original instructions. These are possible choices to discuss, not rules every appointment business should adopt.
Include actions that move information elsewhere, such as downloading a list or sharing a document. Decide what someone needs to take away, who should be allowed to do it and what information the result should include.
If an action needs approval, define what happens before that approval arrives. Does the original arrangement remain in place? Who receives the request? What should a customer see? Answer those business questions before asking for an “approval button.”
Whose information should they be able to use?
Someone’s role is only part of the answer. Also decide which records it covers. A contractor assigned to one visit may need that visit’s details. A regional manager may need bookings for one location. A customer should be limited to the information your business has agreed to show them about their own work.
Use the following worksheet to surface the decisions. Every row is hypothetical and deliberately leaves a question for the business to settle. Replace it with the people and tasks in your own project.
Discuss unusual assignments too. If two contractors share a visit, what must each see? If a colleague covers another location, does access change for a limited period? Write down the exception and who may approve it, rather than relying on someone to lend their account.
| Person and task | Possible access boundary | Decision still needed |
|---|---|---|
| Office colleague arranging visits | Read and update the bookings they coordinate | Which changes need someone else’s approval? |
| Contractor completing an assigned visit | Read that visit’s instructions and add a completion note | When should access begin and end? |
| Customer checking an appointment | Read their own agreed date and customer documents | Which internal notes must stay out of this view? |
| Manager covering another location | Temporary access to that location’s bookings | Who authorises the cover and removes it afterwards? |
What happens when someone’s responsibilities change?
Plan account changes as part of the job. Name the business person who can approve an invitation, change someone’s access and arrange its removal. Make sure there is a clear route for handling a departure or an unexpected absence.
For temporary cover, record why the extra access is needed and when it should be reviewed or end. Ask your supplier how the app will support that arrangement. Do not assume temporary access disappears automatically unless that behaviour is agreed and checked.
OWASP also recommends reviewing access after deployment so people do not accumulate permissions beyond what they need. Choose a review point your business can maintain, and revisit access when someone changes job or an outside assignment finishes.
Think through who takes over unfinished work. Removing a contractor’s access should not leave the office guessing where the visit stands. Agree how the business keeps the necessary work history and who is responsible for the next action.
What should you ask your developer to demonstrate?
Ask for a demonstration using separate practice accounts and made-up records. Try the same appointment as the office colleague, contractor and customer. Check both the work each person should be able to finish and the information or actions that should be unavailable.
Ask how the rules are enforced beyond the visible screen. Hiding a button is not enough: the app must also reject an unauthorised attempt to read or change the record. Ask the supplier how they check this, including attempts to open another person’s record directly.
Try a change in responsibility as well as the initial setup. Remove a practice assignment or account’s access and ask the supplier to demonstrate what happens to an already open session. Record the expected behaviour and anything that still needs resolving.
OWASP recommends testing access rules and refusing access unless it is explicitly allowed. Your worksheet helps describe the intended behaviour; your supplier still needs to implement and verify it. Finish the review with clear answers about who can do what, which cases were checked and who will maintain those decisions after launch.
Write down the access decisions before the build.
Choose one task and work through these questions with the people who understand it. Give your supplier decisions they can implement and examples they can check.
- The person and the job
- Who is trying to finish the task, and which records do they need?
- The allowed actions
- May they read, edit, approve, download or share that information?
- The boundary
- Does access cover their own work, an assigned job, a location or the whole business?
- The change later
- Who approves access, when is it reviewed, and who removes it when it is no longer needed?
Planning something with a similar workflow?
Discuss your project with usA couple of common questions.
Should a manager always be able to see everything?
Discuss what that manager is responsible for and which information supports those decisions. A location manager and a business owner may need different views. Avoid using a senior job title as the only explanation for access to every record or action.
Can we decide the access rules after the app is built?
You can refine them, but agree the main boundaries early. They affect which information appears, who can complete each step and what needs checking. Bring unresolved cases to the supplier before treating the first design as settled, and discuss the effect of later changes on the project.