Private Connections access can now be controlled per organization
Administrators can selectively enable or restrict Private Connections for specific organizations, allowing targeted rollouts and workspace-level access control.
Private Connections can now be enabled or disabled on a per-organization basis. Previously, access to this feature relied on a global toggle or environment variable, making it difficult to restrict visibility or offer the capability to specific customers.
By moving the capability to an organization-level feature flag, administrators can now grant access to individual workspaces. When users navigate to the Private Connections settings in the webapp, the system checks their specific organization's overrides against the global default. If a workspace does not have access, users are automatically redirected away from the settings pages.
The underlying feature flag system was also patched to correctly handle explicit false overrides, ensuring a feature can be strictly disabled for a specific organization even if the global default is true.