Context
We operate multiple brands in one instance. End users (members of an organization) want to subscribe to tickets to track activity.
Current behavior
If a user subscribes from Brand A, they also receive notifications for Brand B tickets (same org, different brand). As a workaround, they must create email rules—not ideal.
Expected behavior
- A subscription taken within a brand context should only cover tickets from that brand.
- No automatic cross-brand notifications unless the user explicitly opts in or an admin sets it.
Impact
- Noise and confusion (irrelevant notifications).
- Brand identity/context mixing.
- Lower engagement (unsubscribes, manual filters) and extra support load.
Acceptance criteria
Subscribing from Brand A results in notifications only for tickets with brand=A.
