From fdce1eeeed2fe370beb3814dc57c11796df9ce71 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Mon, 14 Apr 2025 13:28:14 -0400 Subject: [PATCH 1/2] clarify who receives operational emails --- .../billing/update-billing-operational-contacts.md | 4 ++-- deploy-manage/cloud-organization/operational-emails.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md b/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md index 23650d95d2..aaf2ef468d 100644 --- a/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md +++ b/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md @@ -9,9 +9,9 @@ applies_to: # Update billing and operational contacts [ec-billing-contacts] -If different persons from your organization are involved in billing and operations, you can specify their relevant contact details in addition to the members set up on the account. +If different persons from your organization are involved in billing and operations, you can specify their relevant contact details. These additional contacts only receive billing or operational emails. -These additional contacts only receive billing or operational emails. You can also set a specific email address to receive monitoring alerts. Members of the account still receive both types of emails. +By default, these notifications are sent to all users within an {{ecloud}} organization. If you specify billing and operational email contacts, then only these contacts and the organization owner will receive operational emails. ::::{note} Operational contacts can only receive operational notifications, such as out-of-memory alerts. Operational and billing contacts can’t log in to {{ecloud}}. To log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), you must log in as the [organization owner](/deploy-manage/users-roles/cloud-organization/user-roles.md), or be [a member](/deploy-manage/users-roles/cloud-organization.md) of the organization. diff --git a/deploy-manage/cloud-organization/operational-emails.md b/deploy-manage/cloud-organization/operational-emails.md index 33c40d46e3..9a238d3359 100644 --- a/deploy-manage/cloud-organization/operational-emails.md +++ b/deploy-manage/cloud-organization/operational-emails.md @@ -17,6 +17,6 @@ For high disk usage, an email alert is activated when the space consumed on one We also send an email alert if one of the nodes in your cluster is restarted due to an out-of-memory condition. -These alerts are sent to all users within an {{ecloud}} organization, as well as to the email addresses listed as operational email contacts. This means that an external distribution list or automated service can receive notifications without the need to be added to the organization directly. +By default, these alerts are sent to all users within an {{ecloud}} organization. -To configure recipients external to an {{ecloud}} organization for these notifications, update the list of [operational email contacts](/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md). +Alternatively, you configure recipients external to an {{ecloud}} organization for these notifications by updating the list of [operational email contacts](/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md). These can be any email address, meaning that an external distribution list or automated service can receive notifications without the need to be added to the organization directly. If you specify operational email contacts, then only these contacts and the organization owner will receive operational emails. \ No newline at end of file From d1c20204f40110647c77ef79ee817dc9c90131cc Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Mon, 14 Apr 2025 13:47:14 -0400 Subject: [PATCH 2/2] Update deploy-manage/cloud-organization/operational-emails.md Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> --- deploy-manage/cloud-organization/operational-emails.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/cloud-organization/operational-emails.md b/deploy-manage/cloud-organization/operational-emails.md index 9a238d3359..41108158ae 100644 --- a/deploy-manage/cloud-organization/operational-emails.md +++ b/deploy-manage/cloud-organization/operational-emails.md @@ -19,4 +19,4 @@ We also send an email alert if one of the nodes in your cluster is restarted due By default, these alerts are sent to all users within an {{ecloud}} organization. -Alternatively, you configure recipients external to an {{ecloud}} organization for these notifications by updating the list of [operational email contacts](/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md). These can be any email address, meaning that an external distribution list or automated service can receive notifications without the need to be added to the organization directly. If you specify operational email contacts, then only these contacts and the organization owner will receive operational emails. \ No newline at end of file +Alternatively, you can configure recipients external to an {{ecloud}} organization for these notifications by updating the list of [operational email contacts](/deploy-manage/cloud-organization/billing/update-billing-operational-contacts.md). These can be any email address, meaning that an external distribution list or automated service can receive notifications without the need to be added to the organization directly. If you specify operational email contacts, then only these contacts and the organization owner will receive operational emails. \ No newline at end of file