Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

The customer should have the ability to enable notifications on a certain group and the members of the group should be able to receive the notifications without having to opt-in individually. Currently, after notifications are enabled for a particular group, individual members have to again opt-in to receive such notifications. If the members have not opted in for notifications, they would fail to receive the notifications. 

The goal is to notify the members of the group without them individually having to opt in.

Related customer support ticket:  https://access.redhat.com/support/cases/#/case/03805782

Acceptance Criteria 

These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.

1. Customers should be able to notify different groups regarding various events.
2. The individual members of the group should not go through the process of opting in to receive such notifications. 
3. The individual members should be notified.

Checklist

Open Questions

Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed. 

• Notifications is in the middle of an authorization rework which might have some impact on this feature request. After going through this, we discussed that we probably will take care of this one after the refactor is done, to avoid duplicating the work efforts.