Make it a setting whether Alert and Subscription email recipients are in Bcc or not
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
**Is your feature request related to a problem? Please describe.**
- We have dozens of partnerships managed by several individuals at our organization and, if external recipients don't have easy access to their partnership manager on the email, they may respond to the email directly, sending the request to Metabase administrators, rather than their partnership manager. The partnership manager is typically the right person to do things like add or remove contacts, change report cadence, etc. and they are the internal user on the reports.
- Each subscription is sent to only one corporate entity, but possibly multiple contacts within the organization. The partnership managers are concerned that if the contacts are not visible to one another that they will receive questions and requests from those individuals about who else is receiving the report.
- We were able to disclose all recipients in these subscriptions prior to version 50.
**Describe the solution you'd like**
An option to allow recipients of a subscription or alert to see all of the other recipients.
**Describe alternatives you've considered**
We tried using the "Disclose recipients' setting in Metabase but it did not disclose all recipients - external users still receive individual emails without visible CCs
**How important is this feature to you?**
Internal processes were designed around the recipients being available to one another.
Contributor guide
Research direction
Start by locating the Alert and Subscription email delivery entry points and the existing "Disclose recipients" setting referenced in the issue. Determine how recipient visibility is currently applied, then define the setting's scope and verify that both alert and subscription emails consistently use either Bcc or visible recipients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100