Audience
Name the user and relationship.
Guide / Portals
Define who can see and do what before designing the portal screens.
A customer portal is a secure, role-specific window into selected business records and actions. Before building it, define identity, record-level permissions, authoritative source systems, high-risk actions, support and retention. Start with one complete customer task rather than exposing a large back office through a new interface.
Questionwhat the reader needs
Evidencedefinitions and boundaries
Next stepa useful action path
Why it matters
Audience
Name the user and relationship.
CHAPTER 01
Choose one complete customer task.
A focused first release is easier to secure and test.
Task
Define the request, review or document action.
CHAPTER 02
Design identity and record permission together.
Login alone does not secure data.
Access
Limit records by role and relationship.
Recovery
Protect account and sensitive-action recovery.
CHAPTER 03
Keep source ownership clear.
The portal should not create competing truth.
Read
Expose only approved current data.
Write
Validate actions and show the result.
Continue through the resources system.
Each route answers a different operating question while retaining the same standards for evidence, responsibility and a usable next step.
Route 01
Resources
Use answer-first guides for website, SEO, CRM, automation, dashboards, field technology, portals and AI decisions.Route 02Ai Readable Website Structure
Structure public website information so people, search crawlers and AI-assisted discovery tools can identify entities, services, evidence and answers.Route 03Australia New Zealand Seo Guide
Plan service, industry and location content across Australia and New Zealand without cloned city pages or invented local presence.Route 04Business Automation Examples
Review practical workflow and connected-asset automation examples, including triggers, controls, exceptions and human approval.Route 05Dashboard Design Guide
Define dashboard users, questions, metrics, data lineage, actions and refresh needs before choosing charts.Route 06Field Technology Guide
Plan mobile tasks, offline behaviour, job context, media, synchronisation, review and support for field systems.Route 07Google Sheets Vs Crm
Compare spreadsheets and CRM by ownership, relationships, workflow, permissions, history, automation and reporting needs.Route 08How Ai Assistants Help Businesses
Understand grounded search, summarisation, drafting and extraction use cases with permissions, source visibility and human review.Route 09How Much Does A Business Website Cost
Understand the scope, content, integration, migration, accessibility, performance and support factors that shape website cost.Questions worth resolving
What to clarify before committing.
Do users always need passwords?
No. The identity method follows risk, frequency and task scope.
Can a portal connect to CRM?
Yes when the integration and record permission boundary are defined.
Bring the real problem
Define one secure portal task.
Bring the audience, record source and action that matters.