NoeVault Snip
Product documentation space for embedding issue reporting, screenshot evidence, and requester conversation in NoeVault solutions.
Public product name is NoeVault Snip (short: Snip). Package/SDK identifiers remain historical Snap (@noevault/snap, snap-integration.v1, /p/snap-support* routes) for compatibility.
| Package | @noevault/snap 1.1.3 (identifier retained for compatibility) |
| Marker | PR-8.7E.4A |
| Contract | snap-integration.v1 |
| Reference implementation | KitchenPro.Web |
| Status | Hosted validation PASS (PR-8.7E.4B) |
Learn how to integrate NoeVault Snip into your solutions without creating NoeVault users or consuming seats for external requesters.
| Topic | Page |
|---|---|
| Quick Start | Open |
| Architecture | Open |
| Organisation Onboarding | Open |
| Developer Integration | Open |
| SDK Reference | Open |
| External Requester Identity | Open |
| Category Inheritance | Open |
| Screenshot & Evidence | Open |
| My Requests & Conversation | Open |
| Deployment & Operations | Open |
| Security Validation | Open |
| Troubleshooting | Open |
| KitchenPro Reference | Open |
| Release Notes | Open |
Your authenticated application
→ trusted bootstrap BFF (AppKey server-side only)
→ @noevault/snap
→ SupportTicket system of record
External requesters use ExternalRequester Model B (stable app subjects such as KP-USER-*). They do not receive a NoeVault UserUID, consume seats, or create OLEA records.
Return to the main Documentation hub: Documentation