VeilAppEncryption model, device revocation, auditability, and trust controls.
3 detailed guides
4 min read
Messages are handled as ciphertext/nonce/version payloads, with identity-aware communication context.
• Message bodies are represented with ciphertext, nonce, and version fields.
• Identity context can be conversation-scoped for controlled profile behavior.
3 min read
Remove compromised endpoints from workspace access and enforce revocation across channel activity.
• Marks device as revoked for the workspace security context.
• Can block channel-related operations for revoked devices.
4 min read
Use audit records for visibility and DNS-based domain verification for organizational trust.
• Workspace actions can be stored as audit records.
• Metadata is sanitized to avoid unsafe content exposure in logs.
Browse all categories in the Help Center or contact support if your workflow is not covered yet.