Skip to content

Use restricted crosswalks for safe reviewer row references

Give reviewers operational aliases without treating pseudonyms as anonymity or broader access rights.

Guides

Use restricted crosswalks for safe reviewer row references — what should the operator record?

Review queues sometimes need to refer to rows without exposing the underlying identity to every participant. A local alias can reduce unnecessary disclosure, but the mapping remains sensitive. Keep the crosswalk restricted and make clear that an alias does not authorize resolution or guarantee that the evidence cannot identify someone.

Practical operations check
Give reviewers operational aliases without treating pseudonyms as anonymity or broader access rights.
Create review_row_key unrelated to names or handles, linked to source_key only inside the currently authorized crosswalk. Use aliases that do not encode platform handles, source URLs or meaningful prefixes; an alias carrying those values can disclose the very identity the review view omits.
Follow the approved retention process for mappings and derivative queues, noting that replacing names did not itself anonymize the underlying dataset. If a queue is exported to another system, include it in the retention review so a retired crosswalk does not leave identifying derivative information scattered across unmanaged copies.
01 / Guides

Define the review reference

Create review_row_key unrelated to names or handles, linked to source_key only inside the currently authorized crosswalk. Use aliases that do not encode platform handles, source URLs or meaningful prefixes; an alias carrying those values can disclose the very identity the review view omits.

02 / Guides

Limit crosswalk exposure

Store the alias mapping with the evidence owner and share only the operational fields required by the reviewing role. Keep the crosswalk's audience narrower when appropriate, while recognizing that source text or rare combinations of fields can still identify someone without the direct mapping.

03 / Guides

Test queue usability

Confirm a reviewer can report a schema or state issue using review_row_key without needing the underlying identifying record. A reviewer checking a missing column can report alias R17 and contract failure without receiving the associated account name, demonstrating that the minimized queue remains operationally useful.

04 / Guides

Control resolution requests

Require current authorization before an evidence owner resolves an alias; never publish the mapping in a general issue thread. The evidence owner should record whether resolution is permitted for this specific task, not assume that possession of an alias authorizes every future lookup request.

05 / Guides

Retire aliases responsibly

Follow the approved retention process for mappings and derivative queues, noting that replacing names did not itself anonymize the underlying dataset. If a queue is exported to another system, include it in the retention review so a retired crosswalk does not leave identifying derivative information scattered across unmanaged copies.

Keep the boundaries clear.

  • Give reviewers operational aliases without treating pseudonyms as anonymity or broader access rights.
  • Operational record: Define the review reference. 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.

Know what social media shows about you.
Start with a question.

Get started
montage