Builder Guide
Secure fields
Per-field encryption for your most sensitive data — and what it deliberately turns off.
Any field can be marked secure. Secure field values are encrypted with keys unique to each tenant and are only decrypted at the moment an authorized user explicitly reveals them.
What changes when a field is secure
- Values are stored encrypted; they never sit readable in the database.
- Reading requires an explicit reveal action by an authorized user — values don't display in lists by default.
- The field drops out of search and AI features entirely. Encrypted values are invisible to search indexing and to AI assistants — structurally, not as a setting someone could misconfigure.
The search trade-off is the point, not a limitation to work around. If a field must be searchable, it cannot be a secure field — decide which property matters more for each field before enabling.
What to secure
Good candidates: government ID numbers, bank details, health notes, credential-like values. Poor candidates: names and emails you need to search by, fields that drive workflow branching.
Capability review: 2026-09-14. For exact current technical availability, use the generated API Map and first-class module inventory.