WEB APPS & INTEGRATIONS · 3 MIN READ

Customer Portal Permissions: Logging In Is Only the First Check

Plan customer portal permissions around organisations, records, actions, invitations, and exports rather than treating login as complete access control.

A login establishes who is using a portal. It does not establish which organisation's records that person may view, export, or change.

For a customer portal, access rules belong in the product requirements from the beginning, because they shape the data model and every important operation.

01

Map organisations and memberships

Decide whether a person can belong to one organisation or several. Define who invites colleagues, removes access, and changes roles. A consultant working for two customers may require a deliberate account-switching experience rather than an assumption that every user has one company.

In a hypothetical document portal, a customer administrator might invite a colleague but still lack permission to view a restricted contract. Job title and record access are separate dimensions.

02

Define actions on resources

List view, create, edit, approve, export, and delete separately. Some users may read a record but not change its state. Some actions may depend on the current state, such as editing a draft but not an approved submission.

Laravel's authorization documentation distinguishes authentication from permission to act on a resource and provides gates and policies for these checks. A framework offers structure; it does not decide the business rules automatically.

03

Check every delivery path

Enforce access on the server for page requests, API calls, downloads, and background exports. Hiding a button is helpful interface design but is not the permission check.

A direct file link can bypass an otherwise careful portal if the storage layer serves it publicly. Include attachments, previews, and generated reports in the access map.

Verify that search results, record counts, and error messages do not reveal information belonging to another customer unnecessarily.

04

Handle changing membership

Decide what happens to active sessions, queued exports, and shared links when someone loses access. A report requested yesterday may be generated after the person's permissions change.

Check authorization at the point appropriate to the action, including delivery of sensitive output. Document the intended behaviour instead of letting it depend on whichever code path happens to run first.

05

Test with contrasting accounts

Create representative test users from different organisations and roles. Attempt the same operation with each and check both successful and rejected outcomes. Include direct record identifiers and files, not just the navigation menu.

Keep these tests with the application so future features do not silently widen access. The useful acceptance criterion is precise: the right user can perform the intended action on the intended record, while another user cannot reach it through an alternative path.

06

Discuss the implementation

Explore custom web applications and Laravel development.

KEEP EXPLORING

Sources & further reading

Official documentation for the topics discussed. Check implementation details against the versions and services used by your project.

WRITTEN BY MARKO ARNAUTOVIC

Practical thinking.
Hands-on engineering.

I build AI automation, web platforms, and mobile applications for businesses. These notes share the decisions behind that work.

Meet the engineer behind ArnautCode

PUT THE IDEAS TO WORK

Need help with
the implementation?

Explore the approach and scope for custom web applications.

Explore the service
Chat on WhatsApp