Customer workspace
Show approved requests, milestones, documents and actions relevant to that relationship.
Solution / Controlled access
Give each person a focused window into the work they are allowed to see and do.
A portal provides a secure, role-specific place for customers, staff or partners to exchange information, complete actions and review approved status. GA Applications defines the identity, permissions, records and support model first, then designs a clear responsive experience connected to the appropriate operating systems.
Problemone recurring constraint
Flowpeople, records and hand-offs
Outcomeobservable working change
Why it matters
Customer workspace
Show approved requests, milestones, documents and actions relevant to that relationship.
CHAPTER 01
Design separate journeys around real responsibilities.
Customers, field staff, coordinators and partners should not receive the same navigation or information by default.
Staff workspace
Prioritise assigned work, required evidence and exceptions for the role.
Partner access
Limit shared records by organisation, project, time and purpose.
CHAPTER 02
Make identity, permissions and sensitive actions explicit.
Authentication is only one part of portal security; record-level access, session behaviour and recovery paths also require design.
Access model
Map roles to allowed records and actions, including temporary and delegated access.
High-risk actions
Require suitable re-authentication or approval for consequential changes.
Audit trail
Record important views, submissions and permission changes in proportion to risk.
CHAPTER 03
Support people when self-service is not enough.
The portal must explain status, validation and recovery clearly and provide a visible human support route.
Plain status
Use language that explains what happened, what is waiting and who acts next.
Safe upload
Set file rules, scanning, retention and visibility before requesting documents.
Assisted path
Let a user contact the team with the relevant record context when blocked.
Continue through the solutions system.
Each route answers a different operating question while retaining the same standards for evidence, responsibility and a usable next step.
Route 01
Solutions
Explore practical solutions that connect websites, CRM, automation, dashboards, field tools and AI assistance around a complete business outcome.Route 02Capture And Qualify Enquiries
Connect useful website content, structured forms, CRM ownership and measured follow-up into one dependable enquiry journey.Route 03Quote To Job Workflow
Connect enquiries, scope, quotes, approvals and job setup without losing commercial context or repeating data entry.Route 04Field Evidence And Compliance
Capture job-linked forms, photos, checks and sign-offs in the field with clear ownership, offline resilience and review paths.Route 05Operational Visibility
Create role-specific operational views from agreed definitions, traceable data and clear exception-to-action paths.Route 06Document And Approval Automation
Prepare repeatable documents, route approvals and preserve version and decision evidence with human control where judgement matters.Route 07Connected Assets And Alerts
Connect device signals, thresholds, dashboards and escalation workflows for lights, water, CCTV, barriers, VMS and other operational assets.Route 08Knowledge And Ai Assistance
Help staff find, summarise and draft from approved organisational knowledge with source visibility, permissions and human review.Questions worth resolving
What to clarify before committing.
Can a portal connect to our current CRM or job system?
Yes when the source system provides suitable access. The portal should expose only approved data and actions through a documented integration boundary.
Do customers need a password?
The identity method depends on risk and frequency. Options can include managed accounts, federated sign-in or time-limited links for narrowly scoped low-risk actions.
Can the portal work on mobile?
Yes. Responsive design, touch targets, readable forms and recovery from interrupted connections should be part of the acceptance criteria.
Bring the real problem
Define one audience and one complete portal task.
Show us who needs access, what they must complete and which system owns the result. We can shape a secure first release.