Faith Forge LabsCustom softwareStart with a project brief ↗

Check portal access for the record being requested

A person can be correctly signed in and still be asking for a record they should not see. Authentication establishes an identity. Portal authorization must also establish that this identity may perform this action on this account, project, document or request.

This distinction matters when a portal serves several customers. A role called “customer” describes many users; it does not explain which customer's information belongs to each one.

Write the relationship in ordinary language

Consider a fictional project portal. A customer contact can view documents for projects assigned to their organization. A project-specific guest can view only one project's released documents. Staff can prepare drafts, but drafts are not automatically visible to either customer group.

Those sentences identify several conditions: organization membership, project assignment, document state and action. Turning them into a single broad “logged in” check would lose the actual rule.

Decide how relationships change. A contact may move to a different organization, leave a project or receive a temporary invitation. The application needs a responsible owner for making those changes and a defined effect on existing sessions and links.

Test every route to the information

The same document may appear through a project list, a search result, a preview, a download endpoint or an export. Each path needs to respect the intended boundary. A hidden navigation item is not sufficient protection, and an identifier that is hard to guess does not replace authorization.

OWASP's authorization guidance recommends validating permissions on every request. In a portal project, turn that principle into examples involving actual account and record relationships.

Use two customer accounts with separate harmless records. Open a permitted record, then attempt to reach the other customer's record through the normal interface and direct destinations available in the test. Verify denial without exposing sensitive details about the inaccessible record. Repeat for attachments and exports, not just the page shell.

Include write actions and background work

Viewing a document and approving it are different permissions. Someone allowed to comment may not be allowed to replace the file or invite another user. A background export or notification also needs an appropriate scope; it should not assemble information from every account because it runs outside the visible interface.

Support access deserves its own treatment. Define when staff may inspect a customer's records, which actions they may perform, and what evidence is retained. A universal administrator account shared by the team makes those decisions harder to attribute.

The portal field guide extends this record-level model into invitations, document versions and customer support. Use it alongside a permission table with explicit allowed and denied examples before accepting the portal.