Customer Journey Map

Customer Journey Map

Customer Journey Map

Customer Journey Map

End-to-end path for an organisation using NoeVault. Follow stages in order; skip only when your pilot explicitly says so.

Journey stages

Orient → Organisation → Solution onboarding → Components / environments
→ Users & roles → Groups / SubGroups (routing only)
→ Operation Governance (author policy)
→ Artifact / target → Governed deploy request
→ Approval Center → Execute → Verify health / version / environment
→ Operate → Change management → Recovery (known-good artifact redeploy; first-class Rollback partial)

1. Orient

Read Start Here — NoeVault Orientation and Evaluator Overview. Confirm which reference applications apply to your use case (Lab / KitchenPro / NoeEDMS — not Ascom Pay as primary).

2. Organisation

Create and verify the organisation, then complete Getting Started. Guide: .

3. Solution onboarding

Register the solution and environments you will govern. Tie components to Runtime Registry where required.

4. Users and roles

Invite people in User Management. Assign roles in Role Management. Seats and licenses are separate — see .

5. Groups and SubGroups

Build Groups/SubGroups as membership and routing pools only. They do not grant capability or approval authority. Guide: .

6. Operation Governance

Author the approval policies and process configuration that define how work should be governed. This is not the daily work queue.

7. Artifact, target, request

Prepare the deployment artifact and target. Submit a governed deploy request under the applicable rule.

8. Approval Center

Approvers claim, decide, and record history in Approval Center. Authority to approve comes from Role Management + live DynamicAuthorize — not from SubGroup membership alone. Guide: .

9. Execute and verify

After approval, execute with reauthorization. Confirm health, version, and environment. Fail closed if prerequisites are missing.

10. Operate and change

Use Support / Snip for incidents. Change management returns to OpGov + Approval Center as needed.

11. Recovery

PROVEN_WITH_RESIDUAL as governed redeployment of a previously published immutable artifact (RECOVERY_PROVEN_VIA_IMMUTABLE_ARTIFACT_REDEPLOY). Do not claim first-class Action=Rollback fully certified — that path remains partial (governance/lineage residuals).

Role cheat sheet

Role Typical stages
OrgAdmin / SolutionAdmin 2–7, 10
Approver 8
Deploy engineer 7, 9
Developer Integrates apps; see developer journey
PlatformAdmin Tenant enablement, ops, certification (§11)