feat(block-screen): access-denied block screen for gated-domain users#76
Merged
Conversation
Add the ACCESS_DENIED block type + "You don't have access to Requestly" screen, rendered when a user's per-user block-config carries an `access-denied` entry. Paired with the requestly-cloud change that writes this flag for @aon.com users without BrowserStack IAAM product access. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
wrongsahil
approved these changes
Jul 1, 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.
What
Adds the
ACCESS_DENIEDblock type and its "You don't have access to Requestly" full-screen block, rendered whenever a user's per-userblock-configcarries anaccess-deniedentry (useIsUserBlockedalready applies explicit per-user blocks unconditionally).Why
Free / unlicensed users at a gated domain (Aon) should see a clear "no access" screen instead of a broken app. The decision of who is blocked is made server-side.
Paired change
The requestly-cloud PR writes the
users/{uid}.block-config['access-denied']flag in the BrowserStack user-sync path for@aon.comusers without IAAM product access (requestly-access). This PR is the UI that renders that flag. The two ship together.Notes
access-denied, matching exactly what the cloud writes.isBlocked: false(access granted), the screen clears live via the existing FirestoreonSnapshotlistener.🤖 Generated with Claude Code