Skip to content

feat(block-screen): access-denied block screen for gated-domain users#76

Open
Kanishkrawatt wants to merge 1 commit into
masterfrom
feat/aon-access-denied-block
Open

feat(block-screen): access-denied block screen for gated-domain users#76
Kanishkrawatt wants to merge 1 commit into
masterfrom
feat/aon-access-denied-block

Conversation

@Kanishkrawatt

Copy link
Copy Markdown
Member

What

Adds the ACCESS_DENIED block type and its "You don't have access to Requestly" full-screen block, rendered whenever a user's per-user block-config carries an access-denied entry (useIsUserBlocked already 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.com users without IAAM product access (requestly-access). This PR is the UI that renders that flag. The two ship together.

  • Cloud PR: requestly/requestly-cloud#859

Notes

  • The flag key is access-denied, matching exactly what the cloud writes.
  • Self-correcting: when the cloud flips isBlocked: false (access granted), the screen clears live via the existing Firestore onSnapshot listener.

🤖 Generated with Claude Code

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant