Skip to content
Godwin LawsonBUILDING WITH PURPOSE

Web Development

How Should User Roles and Permissions Work in a School or Business Portal?

How Should User Roles and Permissions Work in a School or Business Portal?

The practical answer

Define access around the work each person must perform, the records they may use and the decisions they may approve. Give each account the minimum necessary permissions, check access on the server and review it when responsibilities change.

A portal can look organised while giving the wrong people access to important records. An admissions officer may need to review application documents, but that does not automatically mean they should edit payment confirmations. A customer should see their own order without seeing another customer’s address.

That is why portal user roles and permissions belong in the project brief. They affect the screens, workflows, testing and handover. They are difficult to treat as a small finishing touch after every department has started using the system.

For web applications and portals, I recommend starting with a responsibility map that the organisation can explain in ordinary language. Technical rules should follow those decisions.

Separate identity, role and permission

An account identifies a person. A role groups responsibilities, such as applicant, reviewer or finance officer. A permission allows an action, such as viewing an application or approving a refund request.

Those concepts are related, but they are not interchangeable. Logging in proves that someone controls an account; it does not prove that the person should open every record behind the login screen.

Access may also depend on a relationship. Two reviewers can share the same role while being assigned different applications. A branch manager may manage staff in one branch without having access to every branch. Write these boundaries down explicitly.

List tasks before inventing role names

Ask each team what they do during an ordinary week and during an exception. Who receives a submission? Who corrects an error? Who authorises a decision? Who needs a report without needing access to the source documents?

Use specific verbs: view, create, edit, assign, approve, export, archive and restore. “Manage applications” is too broad to expose disagreements. One department may interpret it as reading records; another may interpret it as deleting them.

Also identify actions nobody should perform alone. A payment adjustment might require a separate reviewer, while a spelling correction may not. The organisation must decide the approval policy before a developer can implement it consistently.

Build an access matrix everyone can review

The following example is an illustrative planning aid for a school admissions portal. It is not a ready-made policy for every institution.

Responsibility Applicant Admissions reviewer Finance officer System administrator
View an application Own record Assigned records Payment-related details only Only where authorised for support
Edit application answers Before the agreed deadline Approved correction process No No routine editing
Confirm a payment match View own status View status Verify against payment evidence Maintain the integration
Make an admission decision No Only the authorised decision role No No automatic decision authority
Export sensitive records No Only if specifically permitted Limited financial report Separately approved access

An administrator’s technical access deserves particular attention. The person who maintains software does not necessarily have institutional authority to approve admissions, change financial records or make business decisions.

Treat exports and bulk actions as separate permissions

Reading one record and exporting thousands of records have different consequences. The same applies to a bulk status change, a mass message and deletion of an entire category of records.

Discuss what an export contains, who can create it and where it should be stored. An employee who needs a count by programme may not need names, phone numbers and uploaded documents in the same spreadsheet.

Set an approval route for unusual exports. Record the purpose and the person responsible. A downloadable report should support a defined job rather than become an unrestricted copy of the entire portal.

Make the rules work beyond visible menus

Hiding a button can make a screen easier to understand, but it does not enforce access by itself. The server must check whether a person is authorised for the requested action and record.

OWASP recommends minimum necessary privileges, denial by default and checks on requests. Translate those principles into acceptance checks your developer can demonstrate. A reviewer should be unable to access an unassigned record even when they know its address.

Ask how the portal handles changes of role. Removing a menu item should not leave an old session with continuing access. The development team should explain the behaviour for disabled accounts, expired assignments and changed permissions.

Keep meaningful records of important actions

An activity history should help answer a practical question: what changed, who changed it and when? Decide which actions deserve a record, including role changes, approval decisions and sensitive exports.

Avoid putting unnecessary private information into logs. A history entry can identify the affected record and action without copying an entire application document. Agree who can read the history and how a correction is recorded without quietly rewriting earlier events.

This becomes particularly useful when staff disagree about whether an applicant submitted a document or an internal user changed a status. A reliable history supports investigation; it does not replace a clear operating procedure.

Plan account ownership and staff departures

Use individual accounts for staff wherever practical. Shared administrator passwords make responsibility difficult to establish and complicate access removal when someone leaves.

Identify who approves a new account, who checks the requested role and who disables access. Include temporary reviewers, contractors and staff covering leave. Temporary access should have an agreed end or review date.

Schedule a permissions review when responsibilities change and at sensible operational intervals. Ask whether each user still needs the role they hold. Access tends to expand unless somebody owns this review.

Test the boundaries before launch

Include positive and negative checks in your acceptance plan:

  • An applicant can open their own application and cannot open someone else’s.
  • A reviewer can act on assigned records and cannot approve outside their authority.
  • Finance can verify payments without changing academic decisions.
  • A disabled account loses the access the institution expects it to lose.
  • An export includes the agreed fields and excludes unnecessary information.
  • Important actions appear in the activity history with the correct account and time.

The school website versus management system guide helps distinguish public information from private operational work. That distinction is useful when deciding what should sit behind authentication at all.

Frequently asked questions

Should a small organisation create many roles?

Create enough roles to reflect real responsibilities. A long list of nearly identical roles can be hard to maintain. Start with a clear model, then add exceptions only when there is a defined business reason.

Can one person hold more than one role?

Yes, if the organisation permits it and the combination does not defeat an approval control. The system should make the resulting access understandable and reviewable.

Should developers keep administrator access after handover?

Agree the support arrangement explicitly. Identify the access needed, how it is approved and when it is removed or reviewed. Permanent unrestricted access should not be an unexplained consequence of building the portal.

Prepare a useful permissions brief

Before requesting a quote, bring a list of users, record types, important actions and approval boundaries. Mark unresolved decisions. A brief with three honest questions is more useful than a role matrix that looks complete but has never been discussed with the people who will use it.

Further reading

Reference addresses are provided as plain text for copying.

  • https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html

Discuss your next step

Planning a school or business portal? Share the teams involved, the records they manage and the actions that need approval. We can turn those responsibilities into a clear development brief.

Explore web applications and portals

  1. Start on WhatsApp
  2. Send an enquiry through the contact page
  3. Email [email protected]
  4. Call +234 703 799 7791
Lawson Godwin Hezekiah

About Lawson Godwin Hezekiah

Technology entrepreneur, website developer and founder of Mita School and Techmita. I work with businesses, educational institutions, government organisations and NGOs.

Read my story ↗

Keep exploring

Let us work together

Put the ideas into practice.

If your website or digital strategy needs attention, let us discuss a useful next step.