Skip to content

docs: restructure identities page; add PII rule and trait passing guidance#7525

Open
Holmus wants to merge 1 commit into
mainfrom
docs/trait-nature-and-pii
Open

docs: restructure identities page; add PII rule and trait passing guidance#7525
Holmus wants to merge 1 commit into
mainfrom
docs/trait-nature-and-pii

Conversation

@Holmus
Copy link
Copy Markdown
Contributor

@Holmus Holmus commented May 15, 2026

Summary

Restructures docs/flagsmith-concepts/identities.md so the persistent vs transient distinction is presented as a deliberate choice based on the nature of the data, rather than buried as a privacy-edge-case at the bottom of the page. Folds the existing storage / data-store / transient stubs into a single coherent section and adds three pieces of new guidance:

  • PII rule — PII must be transient. The identifier itself must also be non-PII (use UUID / hashed ID, not email or username). Unifying principle: no PII in Flagsmith, anywhere.
  • Cross-service trait sharing — persistent traits let an identity carry trait data the evaluating service does not have direct access to. Pre-associate via the admin API, or set from a separate service.
  • Passing traits at evaluation time — always pass the complete set of traits you have available with each request. For persistent traits the passed value replaces the stored one; for transient traits passing is mandatory.

Also moves Trait Value Data Types ahead of the storage section so traits are fully described before persistence is discussed, and removes the now-redundant Traits Powering Segments one-liner (already covered in the intro).

Anchors preserved: #transient-traits (inbound link from segments/index.md still resolves) and a new #pii anchor.

Closes #6824.

Test plan

  • Confirm docusaurus build passes without new broken-anchor warnings
  • Verify inbound link from segments/index.md#use-transient-traits-for-multi-tenancy to identities#transient-traits still resolves
  • Review the rendered page top-to-bottom for flow

🤖 Generated with Claude Code

@Holmus Holmus requested a review from a team as a code owner May 15, 2026 12:07
@Holmus Holmus requested review from matthewelwell and removed request for a team May 15, 2026 12:07
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

Tip: disable this comment in your organization's Code Review settings.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 15, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 15, 2026 0:10am
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
flagsmith-frontend-preview Ignored Ignored Preview May 15, 2026 0:10am
flagsmith-frontend-staging Ignored Ignored Preview May 15, 2026 0:10am

Request Review

…dance

Reorganises docs/flagsmith-concepts/identities.md so the persistent vs transient choice is a deliberate framing based on the nature of the data, rather than a privacy-edge-case footnote. Folds the existing storage / data-store / transient stubs into a single coherent section.

New guidance:
- PII rule: PII must be transient, including the identifier itself (use UUID / hashed ID, not email or username). Unifying principle: no PII in Flagsmith, anywhere.
- Cross-service trait sharing: persistent traits let an identity carry trait data the evaluating service does not have direct access to (pre-associate via the admin API, or set from a separate service).
- Passing traits at evaluation time: always pass the complete set of traits available. For persistent traits the value replaces the stored one; for transient traits passing is mandatory.

Also moves Trait Value Data Types ahead of the storage section so traits are fully described before persistence is discussed, and removes the now-redundant Traits Powering Segments one-liner.

Anchors preserved: #transient-traits (inbound link from segments/index.md still resolves) and a new #pii anchor.

Closes #6824.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs Documentation updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Frontend: Add granular trait control for client-side SDKs

1 participant