Enterprise customers need more granular control over permissions within Harness. Today, some RBAC permissions can provide access to multiple actions, making it difficult to enforce a true least-privilege model for specific operations.

Requested Enhancement:

Allow administrators to independently control permissions for individual actions within Harness, rather than having multiple actions governed by the same broader permission.

This would provide greater flexibility for organizations that need to restrict specific operations while allowing users to retain access to other related functionality.

Customer Impact:

More granular, action-level permissions would help enterprise customers implement least-privilege access models and better align Harness RBAC with their internal access-control requirements.