本頁將引導您瞭解、設定及管理重要聯絡人，以便接收專案、資料夾和機構資源的重大 Google Cloud 通知。
「重要聯絡人」是一項 Google Cloud 功能，可讓您定義及管理下列類別的重要通知接收對象：
帳單
法律
產品最新動態
安全性
停權
技術
此外，您也可以定義聯絡人，一次接收所有類別的通知。
緊急聯絡人為何重要？
根據預設，Identity and Access Management (IAM) 角色會管理 Google Cloud 資源的權限和存取權控管。不過，指派給這些角色的個人不一定是所有營運通知的最佳聯絡人，尤其是當機構有專責團隊負責帳單、法律或安全等領域時。此外，由於人員和角色異動，如果所有通知都只傳送給預設 IAM 主體，可能會導致您錯過專案或資料夾的重要快訊。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Essential Contacts overview\n\nThis page guides you through understanding, configuring, and managing your\nEssential Contacts for critical Google Cloud notifications from your\nprojects, folders, and organization resources.\n\nEssential Contacts is a Google Cloud feature that lets you define and\nmanage who receives important notifications related to the following categories:\n\n- Billing\n- Legal\n- Product updates\n- Security\n- Suspension\n- Technical\n\nAdditionally, you can define contacts to receive notifications from *all* of\nthese categories at once.\n\nWhy are Essential Contacts important?\n-------------------------------------\n\nBy default, Identity and Access Management (IAM) roles manage permissions and access\ncontrols for Google Cloud resources. However, individuals assigned to these\nroles might not always be the best contacts for all operational notifications,\nespecially when organizations have specialized teams for areas such as billing,\nlegal, or security. Additionally, due to personnel and role changes, relying\nsolely on default IAM principals for all notifications can lead\nto the overlook of crucial alerts about your projects or folders.\n\nEssential Contacts lets you designate custom individuals or teams as\npoints of contact for specific\n[notification categories](#notification-categories). We recommend configuring\nEssential Contacts to make sure important information about your\nGoogle Cloud resources reaches the correct personnel promptly. Think of\nEssential Contacts as a primary contact directory to improve\nresponsiveness and accountability across diverse operational functions. Failure\nto establish and maintain Essential Contacts can result in missed\ncritical notifications within those designated categories.\n\nThe following are some key benefits of configuring Essential Contacts:\n\n- **Receive targeted notifications**: Make sure that designated teams or individuals receive specific messages directly, such as security alerts or billing updates.\n- **Improve reliability and prevent missed notifications**: Reduce the risk of missed notifications because of incorrect contact information.\n- **Maintain operational awareness and compliance**: Establish clear notification channels for operational, security, and compliance issues to support business continuity.\n- **Facilitate proactive management**: Control who gets notified to help you manage your organization effectively, respond to issues promptly, and plan for product changes based on critical updates.\n\nHow do notifications work?\n--------------------------\n\nEssential Contacts acts exclusively as a central directory for your\ncustom contacts, with IAM principals as a fallback if you don't\nconfigure contacts for a specific category. For more information about\nrecommended contacts per category, see\n[Notification categories](#notification-categories).\n\nEssential Contacts only provides contact information that other\nGoogle Cloud services can use, but it doesn't send or manage notification emails\nitself. Individual services retrieve contact details for their purposes and have\ntheir independent permission mechanisms. For example,\n[Advisory Notifications](/advisory-notifications/docs/overview) retrieves details from\nEssential Contacts to display sensitive data from critical\nnotifications within the Google Cloud console, including security and privacy\ninformation. However, you require additional roles to access\nAdvisory Notifications.\n\nEach Google Cloud service determines its own notification needs and specifics,\nincluding message content, sender email addresses, and delivery frequency.\nConsequently, not all Google Cloud offerings use Essential Contacts to\nsend notifications.\n| **Note:** This document doesn't provide a comprehensive list of all services using Essential Contacts, their sender email addresses, or any additional IAM roles to access those services. For detailed information about notifications from specific Google Cloud services, refer to their documentation.\n\nTo help you anticipate who to expect Google Cloud notification emails from,\nsender email addresses end with the `@google.com` address domain. Some\nnotifications for Essential Contacts might include a footer similar to\nthe following to help you identify why you received the message:\n\n*\"You are receiving this message because your administrator has designated you\nas an essential contact for the \u003cvar translate=\"no\"\u003eCATEGORY_NAME\u003c/var\u003e category.\"*\n\nNotification categories\n-----------------------\n\nYou can assign custom contacts to several notification categories. If you don't\nadd a specific contact to a category, notifications in that category typically\ngo to the *fallback contact*, selected based on their IAM role.\nWe strongly recommend adding custom contacts for all relevant categories.\n\nYou can add both individuals and groups as custom contacts. For information on\nbest practices, see\n[Best practices for Essential Contacts](#best-practices).\n\nReview the following table to learn about notification categories, examples of\nnotifications you might receive, recommended recipients, and why using a custom\ncontact is preferable to relying on the fallback.\n\nBest practices for Essential Contacts\n-------------------------------------\n\nFollow these best practices to configure and manage your\nEssential Contacts effectively:\n\n- **Use group aliases, mailing lists, or shared email addresses** : Configure\n distribution lists or group email addresses like\n `security-team@yourcompany.com` or `gcp-billing@yourcompany.com` instead of\n individual email addresses to receive notifications.\n\n This practice significantly reduces the risk of missed notifications because\n of personnel changes and simplifies ongoing management.\n- **Assign custom contacts for every relevant category** : Verify that proper\n contacts are assigned for each [notification category](#notification-categories)\n that is important to your organization to achieve comprehensive coverage.\n\n- **Keep contacts up to date and verify details**: Regularly review and update\n contact information. Periodic review and updates help contacts remain\n current.\n\n | **Important:** Google Cloud cannot automatically detect if an individual contact's email address is no longer valid because of personnel changes, as email addresses can be from any domain. Therefore, establish a regular review cycle to verify and update your Essential Contacts. This practice is critical to make sure notifications reach the intended recipients.\n- **Choose the right resource hierarchy level based on inheritance\n preferences** : You can assign contacts at the project, folder, or\n organization level. Contacts are inherited through the\n [Google Cloud resource hierarchy](/resource-manager/docs/cloud-platform-resource-hierarchy).\n\n As a result, organizational-level contacts receive notifications for the\n organization and all its folders and projects, while folder-level contacts\n receive notifications for that folder and its nested items. Where you assign\n contacts depends on your organization's structure.\n\n Generally, we recommend the following structure based on organizational\n practices, especially for sensitive categories like Billing, Legal, and\n Security:\n\nSupported languages\n-------------------\n\nIn Essential Contacts, each contact has a preferred language setting.\nNotification creators can reference this setting when sending notifications.\n\nWhen you add a contact in the Google Cloud console, the Google Cloud console\nautomatically configures the contact's preferred language based on the contact\ncreator's [preferred language settings](https://console.cloud.google.com/user-preferences/languages).\n\nWhen you add a contact using the API, you manually configure the contact's\npreferred language using a language code. This language code can refer to any of\nthe languages that Essential Contacts supports.\n\nIf a notification is not available in the contact's preferred language, the\nsystem sends it in English.\n\n#### Supported languages\n\n\nWhat's next\n-----------\n\n- [Manage Essential Contacts](/resource-manager/docs/manage-essential-contacts).\n- [Create custom constraints for Essential Contacts](/resource-manager/docs/essentialcontacts-custom-org-policies).\n- Learn how to [associate a domain with a project](/resource-manager/docs/managing-notifications#associate-domain) for verification purposes.\n- Understand how to [manage notification preferences](/resource-manager/docs/managing-notifications#manage-preferences).\n- Learn about [Advisory Notifications](/advisory-notifications/docs/overview)."]]
