NoeVault Snip External Requester Identity

NoeVault Snip External Requester Identity

NoeVault Snip External Requester Identity

NoeVault Snip ExternalRequester Identity Guide

Authority: PR-8.7D ExternalRequester Model B (frozen)
Subjects: Stable application subjects such as KP-USER-*
SoR: SupportTicket

Model B in one page

External app user
   └─ App-authenticated session
         └─ Trusted bootstrap maps to ExternalSubject / ExternalRequester
               └─ SupportTicket owned without NoeVault UserUID
Rule Required behaviour
UserUID Not created for external requesters
Seats Not consumed
OLEA Not created
Ticket ownership ExternalRequester UID + org/solution scope
Continuity Stable subject string (e.g. KitchenPro KP-USER-*) across remounts
Staff actors Real NoeUser UIDs when operators comment from Panel

Evidence you should see on tickets

Field ExternalRequester create Operator reply
Attachment uploadedBy Empty GUID Operator UserUID (if staff upload)
Comment authorUserUID (Customer) Empty GUID —
Comment authorUserUID (Support) — Operator UserUID
createdByName (projection) Trusted ExternalRequester / app label —
authorDisplayName (Customer) Trusted display precedence (not System) —

Actor display precedence (PR-8.7E.4A)

Presentation-only helper — does not write identity:

  1. NoeUser email/username when AuthorUserUID is non-empty
  2. ExternalRequester display name
  3. ExternalRequester email (when privacy rules permit)
  4. Application-specific label (e.g. KitchenPro {role})
  5. Customer / External requester fallbacks
  6. System only for genuine system-generated events

Empty UserUID on an ExternalRequester-owned customer comment must never render as “(system)”.

Account claim

Optional claim flows may link support history to a future NoeVault account. Historical tickets remain keyed to their original ExternalRequester UID — claim does not rewrite ownership into a UserUID create-on-submit model.

Anti-patterns

  • Creating Panel users “so tickets have authors”
  • Treating empty UserUID as a bug on Model B tickets
  • Using System as the default label for customer comments
  • Mixing another organisation’s tickets into My Requests