Preserve table structure when evidence must be withheld — what should the operator record?
A fixed selection may include a row that later cannot be shown. Preserving the historical selection structure does not mean preserving its identifying content. Use a nonidentifying withheld state where policy permits, and never replace the row with another person or object merely to keep a target count looking satisfied.
Remove prohibited identity exposure without filling a withdrawn row's slot with another record.
Record the actual withdrawal or current access result in a restricted operational reference rather than publishing the old identity in an exception description. Use an operational row reference that does not itself reveal the withheld identity; a handle embedded in a ticket title can undermine otherwise correct suppression.
State how many selected slots remain visible and withheld only when those counts are actually observed; do not substitute fresh records or imply the original selection is unchanged in visibility. If a requested count is no longer met by visible records, report that shortfall directly; maintaining a cosmetically full list is not an acceptable reason to substitute members.Identify the visibility decision
Record the actual withdrawal or current access result in a restricted operational reference rather than publishing the old identity in an exception description. Use an operational row reference that does not itself reveal the withheld identity; a handle embedded in a ticket title can undermine otherwise correct suppression.
Separate rank from content
Keep a permitted nonidentifying selection slot and state such as withheld, while removing identity-bearing fields according to current policy. A local slot can retain rank and withheld status only where policy allows that metadata; do not assume historical selection structure overrides a stricter deletion requirement.
Test exported visibility
Inspect both table and download representations; a hidden display cell is insufficient if the JSON or CSV still exposes the withdrawn identity. Check original-link, alternate-name and hidden metadata fields as well as the visible name column, because identity may remain recoverable through those secondary fields.
Check dependent copies
Use approved lineage references to notify authorized owners of affected outputs without attaching the prohibited content to the notification. A notification can name artifact revisions and affected operational slots without reproducing the old source passage or identifying URL in every team's message history.
Report the true shortfall
State how many selected slots remain visible and withheld only when those counts are actually observed; do not substitute fresh records or imply the original selection is unchanged in visibility. If a requested count is no longer met by visible records, report that shortfall directly; maintaining a cosmetically full list is not an acceptable reason to substitute members.
Keep the boundaries clear.
- Remove prohibited identity exposure without filling a withdrawn row's slot with another record.
- Operational record: Identify the visibility decision. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.