You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a sub-organization, the Product Enforcements tab is visible in Organization Settings, and users can interact with the toggle.
However, the update is backed by PATCH /api/v1/organization/:organizationId, which is parent-organization scoped, so sub-org users cannot actually apply the change.
This creates a misleading UI where an unavailable setting appears actionable.
To Reproduce
Log in with a user that has Settings access in a sub-organization.
Switch to a sub-organization context.
Go to Organization Settings.
Open Product Enforcements.
Toggle Unique Secret Sync Destination Policy.
Observe request/response behavior in network and UI feedback.
Expected behavior
Sub-organization users should not be shown root-only controls.
Screen recording
Screen.Recording.2026-03-30.at.11.10.03.PM.mov
Platform you are having the issue on:
Web (Frontend)
Local dev environment (http://localhost:8080)
Browser: Chrome
Additional context
Other root-scoped settings tabs (e.g. SSO, Provisioning, Security) are already hidden for sub-orgs, so this tab is inconsistent with existing UX.
Backend permission enforcement correctly blocks child-org updates for this operation; the issue is frontend visibility/affordance mismatch.
Describe the bug
In a sub-organization, the Product Enforcements tab is visible in Organization Settings, and users can interact with the toggle.
However, the update is backed by
PATCH /api/v1/organization/:organizationId, which is parent-organization scoped, so sub-org users cannot actually apply the change.This creates a misleading UI where an unavailable setting appears actionable.
To Reproduce
Expected behavior
Sub-organization users should not be shown root-only controls.
Screen recording
Screen.Recording.2026-03-30.at.11.10.03.PM.mov
Platform you are having the issue on:
http://localhost:8080)Additional context