NoeVault Snip Organisation Onboarding

NoeVault Snip Organisation Onboarding

NoeVault Snip Organisation Onboarding

NoeVault Snip Organisation Onboarding Manual

Audience: Organisation sponsors, OrgAdmins, Platform operators
Product: support_snap · Runtime: support.snap

Goal

Enable an organisation’s external solution (customer application) to use NoeVault Snip so end users report issues inside that application, while operators work tickets in the NoeVault Panel.

Onboarding sequence

1. Organisation exists in NoeVault
2. External Solution registered (consumer solution)
3. Identity provider / app auth configured for that solution
4. support_snap entitlement applied
5. support.snap capability grains published/enabled
6. Category inheritance verified for the solution
7. Host bootstrap BFF + static Snap assets deployed
8. Controlled pilot validation (anonymous fail-closed + authenticated create)

KitchenPro controlled pilot organisation and KitchenPro.Web solution are the canonical reference for this path.

Roles

Role Responsibility
Platform Admin Catalogue, capability publish, support operations across orgs
OrgAdmin / sponsor Confirm entitlement, users of the external app, pilot feedback
External app owner Bootstrap BFF, asset hosting, app-session auth
Support operators Work SupportTickets in Panel SnapWorkspace

Licensing boundaries (frozen)

Actor Consumes seat? Creates OLEA? Gets UserUID?
External requester via Snap No No No
Panel operator working tickets Per panel licensing Per panel rules Yes (NoeUser)

Do not “fix” ExternalRequester tickets by creating users for every requester.

Categories

Confirm the solution receives the intended effective categories before go-live. Incorrect category lists usually indicate inheritance or publish gaps, not SDK defects.

See .

Acceptance checklist

  • Anonymous bootstrap → SNAP_APP_SESSION_REQUIRED
  • Authenticated user can open Snap, select category, attach/capture, submit
  • Ticket appears for operators under the correct organisation + solution
  • Attachment/comment actors show empty UserUID (Model B)
  • Actor display shows trusted ExternalRequester label — not “(system)”
  • My Requests returns the requester’s tickets only
  • Asset hashes / build markers match the approved package (1.1.3 / PR-8.7E.4A or later approved release)