Skip to content
Internal toolsPublished on 2 min read

Designing roles and permissions for internal software

Turn everyday tasks into a permission matrix for reading, changing, approving and exporting records.

A computer workspace with code and a website on screen

In short

  • A technician may edit their own job sheets and a planner may assign work in their region.
  • Hiding a button helps people find their options.
  • Define who assigns access, when temporary permissions expire and how to handle departures.
  • Next steps

Define each action and its scope

A technician may edit their own job sheets and a planner may assign work in their region. Separate viewing, exporting, deleting and approving. Put actions down the rows and roles across the columns. Give each role only the access it needs.

Enforce the rule on the server

Hiding a button helps people find their options. Direct URLs and export requests still need an access check. Use accounts with one role when testing. Include a legitimate account attempting to reach another organisation’s record.

Plan for people changing roles

Define who assigns access, when temporary permissions expire and how to handle departures. Check what happens to existing sessions after revocation. Record changes and review administrative accounts periodically.

Next steps

Creagrid / actie

Practical checklist

  • Describe the problem and intended outcome.

  • Involve the people who use the process every day.

  • Test the riskiest assumption with a small prototype.

  • Define tests, ownership and maintenance up front.

From insight to software

A digital product that genuinely fits your organisation?

We bring process, users and technology together in one feasible product plan.Discuss your challenge
Book a call

Choose a time

Creagrid team member · 15 minutes on Microsoft Teams

Open the calendar on a separate page