Conversation
Elevate the existing note about unencrypted Search Attributes to a caution admonition with expanded guidance covering both attribute names and values. Add reasoning about compliance risk (GDPR, HIPAA, SOC 2) and recommend using opaque identifiers instead. Cross-reference the warning from the Default Search Attributes section. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
dustin-temporal
commented
Mar 17, 2026
dustin-temporal
commented
Mar 17, 2026
Workflow Ids and other user-defined identifiers (Workflow Type, Task Queue, Activity, Signal/Query/Update names) are stored in plain text and bypass the Payload Codec. Add a caution admonition warning against using PII directly as a Workflow Id, with compliance reasoning (GDPR, HIPAA, SOC 2). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dustin-temporal
changed the title
lennessyy
approved these changes
Mar 17, 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.
Summary
:::noteabout unencrypted Search Attributes to a:::cautionadmonition with a clear titleWhy
The existing docs had a brief, easy-to-miss note that Search Attribute values are unencrypted. The guidance about not using PII in attribute names was buried in a bullet list under Default Search Attributes. Users working with sensitive data (healthcare, finance) need prominent, actionable guidance with compliance reasoning to make the case internally for proper data handling.
Test plan
:::cautionadmonition renders correctly[warning above](#search-attribute)anchor link resolves correctly[Payload Codec](/dataconversion#payload-codec)link resolves correctlyyarn check-links🤖 Generated with Claude Code
┆Attachments: EDU-6059 Strengthen Search Attribute guidance on sensitive data and PII