Start Here - NoeVault Orientation

Start Here - NoeVault Orientation

Start Here - NoeVault Orientation

Start Here — NoeVault Orientation

Welcome to NoeVault. This page orients you to the product surfaces you will use day to day. You do not need engineering history or PR chronologies to run a tenant.

What NoeVault is

NoeVault is a governed platform for organisations to:

  1. Onboard a tenant and solutions
  2. License capabilities and assign people
  3. Author approval policies and process work
  4. Deploy artifacts under governance
  5. Embed support capture with NoeVault Snip (Snip; internal id support.snap retained)

Pick your path

Goal Open
See the full customer path Customer Journey Map
Evaluate fit before buying Evaluator Overview
Browse the documentation set Documentation
Stand up an organisation
Integrate Auth / Logging / Snip / Packages
Understand who can approve what
Deploy under policy

Core surfaces (UI names)

Surface What it is for
Getting Started OrgAdmin onboarding home
App Gallery Discover and open licensed applications
User Management People, Groups, SubGroups (membership / routing pools)
Role Management Authority (roles and solution role rights)
License Workspace Entitlement composition and publish
Capability Studio Capability catalogue authoring (platform)
Runtime Registry Runtime / client registration
Operation Governance Policy and process authoring
Approval Center Approval work queue, decisions, history
NoeVault Snip Embedded support requests and evidence

Mental model (non-negotiable)

Runtime Registry → Capability Studio → License Workspace → Role Management
→ User Management → EffectiveAccessCompiler (shadow) → DynamicAuthorize (live)
  • Membership in a Group or SubGroup does not grant capability.
  • Being on a routing list does not authorize an action by itself.
  • Navigation visibility is a projection — not a second authority engine.

Honesty

  • Packages setup: PARTIAL (see ).
  • Governed recovery: PROVEN_WITH_RESIDUAL via immutable artifact redeploy (4E.50B); first-class Action=Rollback remains partial.
  • Phase 16 certification evidence is CLOSED — use the customer deployment journey, not retest scripts.