Product & data owners
The lifecycle of a field
Follow a synthetic process temperature from collection through tokenization to approved use. See who can receive the value and when.
Resources / Technical reading
Explore the product mechanism, policy boundaries and VISCOR reference integration from the perspective of your evaluation team.
Reading guide
Product & data owners
Follow a synthetic process temperature from collection through tokenization to approved use. See who can receive the value and when.
Security & governance
Review encryption, field authorization, audit scope and attestation status before a technical assessment.
Platform & integration engineers
Review ownership of service identities, event catch-up, field release and usage reconciliation.
Terms in practice
A · field token
An opaque reference to a protected field. The caller still needs authorization before it can receive the original value.
B · purpose
A registered reason for processing data, such as quality auditing. The requested purpose is checked against the grant and processing basis.
C · workload
A program or model job that performs a specific task. Each deployment uses a managed service identity to request fields within its grant.
Select a type and purpose, explore the product example and define an initial proof of concept.