Repository navigation
feat(foxy-user-invitation-form): grant customer anonymization as a write-only scope - #294
Open
brettflorio wants to merge 2 commits into
Open
brettflorio wants to merge 2 commits into
brettflorio wants to merge 2 commits into
Conversation
|
Brett Florio seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
pheekus
self-requested a review
November 12, 2026 17:56
pheekus
requested changes
Nov 12, 2026
pheekus
left a comment
Contributor
There was a problem hiding this comment.
Changes requested via a private channel.
…ite-only scope The API added `customer_anonymizations_write`, a store scope with no read counterpart that allows irreversible customer anonymization and is needed to turn on or change automatic anonymization. User invitations: - New WRITE_ONLY list (a subset of COLLECTIONS, like RESENDABLE) with `customer_anonymizations`. - The custom matrix offers only None and Full for a write-only row, and Full writes the write token alone. The read preset leaves it out. - Only a granter holding the write token or store_full_access can grant it. - The card lists it under full access, never under read-only. Store form: - The data retention section is read-only when the current user's scope restricts collections and lacks `customer_anonymizations_write`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ad preset parseScope, canGrantReadPreset and the scope control each spelled out the read preset's level for a write-only collection; they now share it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
brettflorio
force-pushed
the
feat/customer-anonymizations-scope
branch
from
November 12, 2026 19:30
5550acd to
f041521
Compare
pheekus
approved these changes
Nov 12, 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
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.
The API has a new store scope,
customer_anonymizations_write. It is write-only: there is no_readtoken, and the API rejects one. It allows irreversible customer anonymization, and it is needed to turn a store's auto-anonymize on or change its window.User invitations
customer_anonymizations_writealone.store_full_access. If an invitation already has the scope and the editor lacks it, the scope control locks, as it does for any other grant they can't give.WRITE_ONLYlist, a subset ofCOLLECTIONSin the same wayRESENDABLEis, matching the API's write-only collections.StoreForm
customer_anonymizations_write, matching the API, which refuses anydata_retentionchange without that scope. Unrestricted scopes are unchanged.Tests
wtrgroups in the Playwright image:All pass, as do eslint, prettier and
tsc --noEmit.Linear: FX-40
🤖 Generated with Claude Code