✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Summary

This PR removes frontend-only SCIM guards that were previously blocking user deletion, deactivation, and activation at the organization level when currentOrg?.scimEnabled was true. The guards produced error notifications and returned early, preventing admins from managing users through Infisical's UI even when the backend may have permitted the operations.

Key changes:

• OrgMembersSection.tsx: Removes the allowedLabel tooltip message and the currentOrg?.scimEnabled condition from the bulk-delete button's isDisabled prop.
• OrgMembersTable.tsx: Removes two early-exit SCIM blocks from the per-row activate/deactivate and remove-user click handlers.
• UserDetailsByIDPage.tsx: Removes two equivalent early-exit SCIM blocks from the user details page dropdown handlers.

No new logic is introduced, no imports are left dangling, and currentOrg remains in use in all three files for other purposes. The change is consistent and leaves authorization entirely to the permission system (OrgPermissionCan) and backend enforcement.

Confidence Score: 5/5

• This PR is safe to merge — it is a pure removal of redundant frontend guards with no new logic introduced.
• The changes are straightforward deletions of frontend early-exit checks. All three files remain logically consistent after the removal, no imports become unused, and authorization is still enforced by the existing OrgPermissionCan wrappers and backend layer. No security regressions are introduced.
• No files require special attention.

_{Last reviewed commit: 97caf90}

@greptile re-review this PR