Secure Customer Portals
Secure Customer Portals: Role-Based Access Control And Data Privacy For Regulated Brands
A client needs to upload a sensitive document. Your team needs to review it. A manager needs to approve the next step. And an external auditor may eventually need to see a record of what happened.
Sounds straightforward. Until the document is sitting in an email thread with six attachments, three versions and a former employee still copied on the conversation.
Re: Fwd: Re: Fwd: Application documents (final)
- From
- Your client
- To
- ReviewerManagerSupport
- Cc
- Former employee Left the company
- application.pdf
- id-scan.jpg
- statement-v1.pdf
- statement-v2.pdf
- statement-final.pdf
- signed-form.pdf
“Please keep this confidential.”
For businesses handling sensitive information, the way customers share and access that information matters. A customer portal can make the experience smoother, while giving the business a more deliberate way to manage access, activity and privacy.
At Clickative, we build custom portals and applications around the people who use them and the information they need to handle. That includes thinking about what happens after someone clicks “Log in.”
01After Login
The Real Question Starts After Login
Imagine a financial services business with a customer portal. A client uploads a document for an application. The client expects it to reach the right people, and only the right people.
Now consider everyone who might use that portal:
Customer
Needs access to their own application.
Team Member
Reviews cases assigned to them.
Manager
Approves decisions for their team.
Auditor
May need authorised access to selected records.
Administrator
Manages parts of the system.
They all need an account, but they don’t all need the same view. Even people with the same job title may need access to different records.
A login tells the system who you are. Access rules determine what you can do once you’re inside.
That distinction is the starting point for a portal designed around privacy.
02What Is RBAC?
What Is Role-Based Access Control?
Role-based access control, usually shortened to RBAC, is a way to organise permissions around responsibilities.
Instead of deciding every permission separately for every person, a business can define roles with appropriate capabilities and assign users to them. A customer role might allow someone to upload and view documents. A reviewer role might allow an authorised team member to assess submissions.
NIST describes roles as collections of permissions assigned to users, with rules governing which actions those roles can perform.1
Here’s how that might look in our hypothetical portal:
| Role | Example Access |
|---|---|
| Customer | View their own application and upload requested documents |
| Reviewer | Review documents for assigned applications |
| Manager | Review and approve cases within their authorised team |
| Auditor | View selected records made available for an authorised review |
| Administrator | Manage designated system settings and user access |
The important word is “example”. Every business has its own responsibilities and boundaries.
When we plan a portal, we work through those boundaries with the client: who needs access, what they need to do and which information should remain outside their view.
03Beyond The Role
The Right Role Is Only Part Of The Answer
Giving someone the title “reviewer” doesn’t automatically answer which documents they should see.
Consider two reviewers working for the same business. They may have the same role and the same general ability to review applications, but each should see only the cases their organisation has authorised them to handle.
That means a useful access decision can involve several questions:
- Who Is AskingWho is requesting access?
- What ActionWhat action are they trying to take?
- Which RecordWhich customer, document or account is involved?
- Is It PermittedDoes their role and relationship to that record permit the action?
Those checks matter for viewing a page, downloading a document, changing an account and accessing information through an integration.
A polished interface might hide a button from someone who shouldn’t use it. The underlying system also needs to check the request itself. OWASP recommends checking authorisation on every request and keeping access decisions on trusted system components.2
That behind-the-scenes work gives the design its foundation.
04Least Privilege
Give People What They Need. Keep The Rest Private.
There’s a useful principle behind all of this: least privilege.
It means giving a person the access needed for their responsibilities, rather than opening everything up by default. NIST defines the principle in terms of the minimum privileges needed to carry out an assigned task.3
For example, a support person might be able to help with an account without seeing every sensitive document.
And when someone’s responsibilities change, their access needs to change too.
A contractor finishes a project. An employee moves to another team. Those are moments to revisit the access they were granted.
When we design an administration interface, we consider how the people responsible can understand and manage those permissions without turning the process into a guessing game.
05Privacy By Design
Privacy Starts Before The First Document Is Uploaded
A secure portal is also shaped by what it asks people to share.
Does the business need every field in that form? Who needs to see the uploaded file? How long should the information remain available? Which connected services will handle it?
The UK Information Commissioner’s Office describes data protection by design as considering privacy from the beginning and throughout a product’s lifecycle. Its guidance also points to collecting and using only the information needed for a specific purpose.4
For a portal project, that conversation can cover:
- CollectionWhat information is actually needed?
- VisibilityWho needs to see each part?
- StorageWhere will the information and backups live?
- RetentionHow long should records be kept, considering applicable obligations?
- SharingWhich providers or integrations receive the data?
- RemovalHow will eligible records be deleted when they are no longer needed?
The answers depend on the organisation and its obligations. Bringing them into the planning stage makes them part of the product’s design, alongside the dashboard and the upload button.
06A Document’s Journey
Following A Document Through The Portal
Let’s return to our hypothetical financial services client.
They sign in and upload the document requested for their application. The portal confirms the upload, shows its status and gives the client a clear place to return if more information is needed.
Behind the scenes, the workflow might look like this:
-
Filed In The Right Place
The document is connected to the correct application.
-
Seen By The Right Reviewer
An authorised reviewer sees it in their assigned work.
-
Approved By A Manager
A manager is notified when a decision needs approval.
-
Recorded For Review
The relevant activity is recorded for an authorised review.
-
The Client Stays Informed
The client sees a useful status update without seeing internal-only notes.
If the reviewer leaves the organisation, their access should be removed through the business’s account management process. If the client needs help, support staff should have the appropriate level of access for that task.
The details differ by business. Each person needs a clear next step, with their information handled carefully.
07Security Details
The Security Details Behind A Smooth Experience
A portal can look simple because the complicated work is happening underneath.
Depending on the project, the design may include measures such as:
Stronger Sign-In
Such as multi-factor authentication where appropriate.
Permission Checks
Applied to requests for pages, records and files.
Protected Data
Appropriate encryption for information in transit and at rest.
Activity Records
Useful logs of relevant events and access changes.
Careful Administration
Processes for granting, reviewing and removing access.
Ongoing Attention
Updates, monitoring and review after launch.
Logs need their own privacy considerations. Recording that an authorised user accessed a document may be useful; copying the document’s contents into a log usually creates more sensitive information to manage. OWASP advises considering what data should be excluded from logs.5
The goal is an experience that feels clear to customers and manageable for the people responsible for it.
08Compliance
What About Compliance?
For a regulated brand, this is where the conversation gets specific.
A healthcare organisation, a financial services company and a business operating across several countries may face very different obligations. Requirements can also depend on the information involved, the services used and where the business operates.
A thoughtfully designed portal can support an organisation’s privacy and security programme. Compliance also involves its policies, staff, providers, contracts, operations and the rules that apply to it.
When we work on a project with regulatory requirements, those requirements need to be identified and agreed as part of the scope, with the client’s legal, privacy or compliance advisers involved as appropriate.
The right question is: what does this particular business need its portal to do, and how does that fit into its wider responsibilities?
09How We Build It
How We Bring The Portal To Life
A secure customer portal still needs to be a good customer portal.
Clients should know what to upload and what happens next. Staff should find their work easily, and administrators should understand the access they’re managing.
Our process brings those pieces together:
Imagine
Understand the users, information, responsibilities and project goals.
Design
Shape clear journeys and interfaces for the people using the portal.
Build
Connect the application, data and access rules around the agreed requirements.
Refine
Review and test the experience, including what happens when access is denied or a workflow changes.
We use AI to support parts of development, including research, code drafts and testing. Our team guides the architecture, security review and user experience decisions.
The result should give people a clear way to do what they came to do, with thoughtful controls working in the background.
Give Your Customers A Better Way In
Sensitive information deserves more than a crowded inbox and a hopeful “please keep this confidential.”
If your customers need to share documents, track progress or work with your team in a private space, a custom portal can bring those interactions together around your business.
Tell us what you’re building. We’ll put together a FREE concept proposal with visual directions and functional ideas for you to explore before committing.