RBAC for alert visibility, actionability, and group/incident behavior

[Full description of desired product behavior is in the attached file]

Customers require desired an operating model that separates who can see an alert from who can manage an alert. A user may need broad visibility into alerts for awareness, coordination, and situational context, while management actions should remain limited to the smaller set of alerts that the user or team actually owns.

In addition, when alerts are grouped or rolled up into an incident, users need enough visibility to understand the complete context of the group. Watson 4.x applies restriction filters even inside grouped or incident views, which can result in a mismatch between the visible alert list and the total alert count displayed for the group.

The requirement is therefore not just about security. It is also about operational usability. The platform should preserve broad context and awareness where appropriate, while still enforcing narrow action rights on only the alerts a user owns.

Cloud Pak for AIOps needs to support an operational model built on three related principles: 

1.     Visibility and actionability are independent. Users may need broad access to alerts for awareness, situational context, and coordination, while management actions must remain limited to alerts the user or team actually owns. Granting visibility should not automatically grant management rights. 

2.     Context menu actions in the Alert Viewer should be authorized at the per-alert, per-action level. The right-click context menu is the primary operational surface. The platform should evaluate whether a given user is authorized to perform each specific action on each specific alert, not just whether the user holds a management role globally. When an action is blocked, it should be presented as disabled with a brief explanation rather than silently removed.

3.     Grouped and incident views should preserve full operational context. When alerts are grouped or rolled up into an incident, operators must be able to understand the complete scope of participating alerts. If restriction filters reduce the visible list, the platform should make that filtering explicit and consistent with all counts and badges shown in the UI. Ideally, a supported mechanism, such as a toggle, allows operators to switch between their personal filtered view and the full group context.