Customer has reported that users assigned the ccm-viewer role can still perform Start and Stop actions on servers from the CCM Autostopping Rules UI.

Since the ccm-viewer role is intended for view-only access, the customer expects users with this role to be restricted from performing operational actions that modify server states.

The customer was previously informed that this behavior is by design. However, they would like to revisit this functionality and have Start/Stop actions restricted for users with view-only access.

Current Behavior

Users assigned the ccm-viewer role can access the Autostopping Rules UI.

These users can perform Start and Stop actions on servers.

There is currently no effective restriction preventing view-only users from triggering these operations.

Expected Behavior

Users assigned the ccm-viewer role should have read-only access to CCM Autostopping.

Start and Stop actions should be hidden or disabled for users with view-only permissions.

Only users with the appropriate permissions should be allowed to perform Start/Stop operations.

Backend authorization should also enforce these restrictions to prevent unauthorized actions through API requests.

Enhancement Request

Introduce granular RBAC control for Start and Stop operations in CCM Autostopping.

The enhancement should:

Separate operational permissions (Start/Stop) from view-only permissions.

Restrict Start/Stop actions for users assigned the ccm-viewer role.

Ensure the UI and backend APIs consistently enforce the assigned permissions.

Allow administrators to grant operational permissions independently of read-only access.

Business Impact

This limitation prevents customers from enforcing a strict separation between users who can monitor Autostopping configurations and users who are authorized to perform operational actions.

For NYLI, this is an important access-control requirement to ensure that users with view-only access cannot inadvertently start or stop infrastructure resources.