Customer and dealer portals
Specify login, orders, documents, access and support across the boundary between external users and internal systems.
Author：WeTech technical team · Updated： (Hong Kong time (GMT+8))
Define what external users may view, submit and change before designing login, organisation permissions and integrations. Prioritise customer isolation, revocation, document downloads and submission state. An internal administration screen should not simply be exposed as a customer portal.
When to use this guide
For businesses handling repeated order-status, document-download or application enquiries by email.
Portal procurement checklist
| Feature | Confirm | Essential test |
|---|---|---|
| Organisations and users | Invitations, roles, offboarding | Customer and dealer isolation |
| Orders and status | Source and freshness | Stale, cancelled, restricted records |
| Documents and submission | File rules, review, retention | Unauthorised downloads, duplicates |
| Support | Notifications, exceptions, contact | Delivery failure and human handoff |
Start with a complete customer task
Choose status lookup, approved-document download or submission and define both customer and staff steps. If the source cannot refresh quickly, show freshness and a contact route instead of presenting stale information as live.
Test isolation directly
Test links, search, attachments and exports with different customers, roles, revoked and signed-out users. Hiding a button is not an access control; APIs must enforce record access. Include forwarded invitations and account recovery in the test plan.
Keep submission and support state
Successful submissions need a verifiable identifier and state. A notification failure must not create another application. Separate internal review from external display and correction so customers understand the next step rather than seeing only a generic sent message.
Illustrative scenario
Hypothetical portal: dealers view their own organisation’s orders and documents while staff approve amendments. Test two dealer accounts against each other’s document links before launch. This example does not imply a delivered WeTech client portal.
Frequently asked questions
Does login establish isolation?
No. Verify organisation, role and record-level access as well.
Does a portal require a mobile app?
Compare responsive web and PWA options against the required device capabilities.
Can we expose internal records directly?
Define external scope, masking and approval rules; do not assume all records are public.
Brand and public case scope
WeTech Consulting, also called WeTech or WeTech AI HK, provides AI and IT consulting in Hong Kong. WeProperty HK and WeCredit HK are self-developed products. Their cases support the observable features listed: property, estate and transaction-reference entry points for WeProperty; submission, review and public-data masking for WeCredit. WeCredit is not a TU credit-rating service or a final determination of facts.
WeProperty HK · WeCredit HK (case studies in Traditional Chinese)
Reference sources
- PCPD：Artificial Intelligence: Model Personal Data Protection Framework
- GOV.UK Service Manual: Writing user stories
Official documents support the technical, risk and measurement concepts. Checklists, estimation methods and illustrative scenarios are WeTech planning recommendations, not official prices or client results. Check the supplier’s current plan and terms. Sources reviewed: (GMT+8)
Related guides
Discuss your project
Share your workflow, systems and goals. We will review scope before discussing deliverables, acceptance and a quotation.
Request an initial consultationExplore this service