System capability
Customer portal
A private place for customers to see their requests, documents and next steps.
Discuss your projectThe workflow
Identity → authorized records → request → status change → notification
The boundary that matters
Authorization must be checked for every server-side record access. Hiding a menu item is not a permission check. Decide which internal notes should never be exposed to customers.
How this capability is scoped
We agree the records, actors, transitions and exceptions before implementation. A capability can be built into a new platform or connected to an existing tool where its API and operational model allow it. It is a family of engineering patterns, not an off-the-shelf product with a universal feature list.
Acceptance checks
Trace the normal workflow and at least one failure at each handoff. Confirm which role can act, what state is saved, what the customer sees and how staff recover. Integration credentials, migration, hosting and support are included only when agreed in the project scope.
Questions, answered
Before we build.
Is this a ready-made product?
This page describes a capability URVEON can scope into a project. FastBook is a separate venture; custom implementations have their own requirements and terms.
Can this connect to our existing tools?
We assess the existing tool’s API, account access, data ownership and failure behavior before confirming an integration.