Hiding sensitive data in the UI
Thunks that handle personal or confidential information can hide that content in the product UI until someone deliberately shows it. This is useful when you share a screen, leave a thunk open on a desk, or review work with people who should not see every chat message or field value by default.
Important: this is UI concealment only. It does not delete, encrypt, or change what is stored. Anyone with access who reveals the content can see the real values. Mark fields and enable chat hiding separately — they are independent.
What you can hide
What | How you turn it on |
Chat messages and AI summaries | Security Guardian setting Chat messages may contain sensitive information |
Individual property values (grids, detail views) | Property option Sensitive data on that field |
The eye control in the thunk header appears when either option is in use.
Hide chat messages
Open the thunk’s Settings.
Open the AI Governance area and choose Security Guardian.
Turn on Chat messages may contain sensitive information.
When this is on, chat bodies and AI summaries show as a masked placeholder until you reveal them. Message chrome that is safe to leave visible — for example step headers, “Done”, or that a tool was called — can still appear; the sensitive text itself stays hidden.
If Security Guardian options are grayed out or show an upgrade notice, your plan does not include this control.
Mark a field as sensitive
When you edit a property in the thunk’s data structure, turn on Sensitive data. The option’s description is: hide this value in the UI by default.
Sensitive field values appear as a masked placeholder with a small eye control next to that value. Revealing one field does not reveal chat messages, and revealing chat does not reveal every sensitive field.
How to show hidden content
There are three layers of control:
Thunk header eye — shows or hides all sensitive content for this thunk (chat and marked fields). Use this when you want everything visible while you work, then hide it again when you are done.
Chat banner — Show sensitive data — appears in the chat pane when chat hiding is on and the header eye is still set to hide. It only affects chat messages and AI summaries in that pane.
Per-field eye — next to a masked property value; reveals that one value.
While the header eye is set to show everything, the chat banner and field masks stay out of the way.
Practical tips
Turn on chat hiding for thunks where agent logs or conversations may include personal data, secrets, or confidential attachments text.
Mark only the columns that truly need it (for example SSN, account number, or medical notes) so everyday status fields stay readable.
Remember that collaborators who can open the thunk can also use the reveal controls — this is not a substitute for access control or for data retention when you need data to leave the system.
What this does not do
It does not redact data in exports, APIs, or stored workflow records.
It does not replace who can open the thunk (owners, admins, participants, and end users still follow normal access rules).
It does not automatically mark fields as sensitive when you enable chat hiding — set each field you care about.