A business intelligence team is configuring data-driven alerts on key performance charts within Looker Studio Pro to notify internal stakeholders whenever sales targets fall below a specific threshold. Which requirement must be met when configuring the recipients and conditions for these chart alerts?

Alert recipients must belong to the organization, and a single alert can include up to 50 email addresses.: ### **What Data-Driven Alerts Are in Looker Studio Pro** **Looker Studio Pro** enables report editors and viewers to set up automated **data-driven alerts** directly on chart components. When the underlying data crosses a predefined threshold—such as sales dropping below a minimum KPI target or web traffic spiking—the platform automatically sends email notifications to designated users. ### **How it Meets the Requirement** - **Organizational membership enforcement (✓):** Looker Studio Pro requires all email recipients added to an alert configuration to be verified members of the same organization's workspace domain. External domain addresses, external aliases, and third-party email lists cannot be added to alert distributions. - **Recipient scale limit (✓):** An alert allows adding up to **50 email addresses** per alert configuration, providing ample coverage for team leads, analysts, and project stakeholders who need visibility into metric changes. - **Automatic creator inclusion (✓):** The individual creating the alert is automatically enrolled as an active recipient, ensuring that the alert owner stays informed whenever a trigger event occurs. ### **Key Advantages and Capabilities** - **Proactive monitoring:** Keeps business teams informed immediately when critical business metrics change without requiring manual dashboard checks. - **Granular alert conditions:** Supports threshold comparisons (such as *greater than*, *less than*, or *equal to*) evaluated against baseline data. - **Enterprise security compliance:** Enforcing intra-organization recipient rules prevents proprietary business intelligence metrics from being accidentally delivered to external addresses. - **Centralized management:** Report administrators can monitor, toggle, or deactivate alerts across the entire report via access settings. ### **Why This Option Is Optimal** This configuration aligns directly with the architectural constraints and governance model built into business intelligence alert mechanisms. It enforces enterprise data privacy while supporting broad distribution across internal operational teams.