Merged
Conversation
Auto Run document covering all pages that need to be created or updated to reflect the new field masking feature: mask-a-field, understanding-field-status, field-status-faq, source-record, data-preview, export-operation, materialize-operation, and field-status-api. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Documents where masking is applied (data preview, anomaly source records, field profile histograms, anomaly assertion context, export field profiles, and materialize snapshots) and how masked values can be revealed (UI surfaces) vs. where they cannot (assertion context, enrichment datastore outputs). Updated pages: - mask-a-field.md: full surface table, reveal section, unmask coverage - understanding-field-status.md: expanded sensitive data protection - field-status-faq.md: updated masking FAQ + 2 new entries - source-record.md: masked fields section - data-preview.md: masked fields section - export-operation.md: field masking and export section - materialize-operation.md: field masking and materialize section Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Source record reveal toggling applies to all records attached to an anomaly at once, not individually per-record. Updated all doc surfaces where the inaccurate per-record language appeared. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
… the UI qualifier
Replace all references to the literal `***MASKED***` placeholder with
plain language ("obfuscated") per documentation style guidance.
Also remove the "in the UI" qualifier from audit log callouts — reveal
behavior and logging apply platform-wide, not only to UI interactions.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…rations Export and Materialize operations do support revealed values via the include_masked API parameter — they do not require unmasking the field first. Updated all doc surfaces to accurately reflect that include_masked is available on the API but not exposed in the UI. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
RafaelOsiro
changed the title
RafaelOsiro
requested changes
Mar 20, 2026
Contributor
RafaelOsiro
left a comment
RafaelOsiro
left a comment
There was a problem hiding this comment.
The content is ready.
The links have been tested.
I just found a strange file (possibly related to Maestro) that I don't think should be included in the project.
RafaelOsiro
approved these changes
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document use of Field masking and impact