[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-05-15。"],[],[],null,["# Organization structure\n\nThe root node for managing resources in Google Cloud is the\n[organization](/resource-manager/docs/cloud-platform-resource-hierarchy#organizations).\nThe Google Cloud organization provides a\n[resource hierarchy](/resource-manager/docs/cloud-platform-resource-hierarchy)\nthat provides an ownership structure for resources and attachment points for\n[organization policies](/resource-manager/docs/organization-policy/overview)\nand access controls. The resource hierarchy consists of folders, projects, and\nresources, and it defines the structure and use of Google Cloud services within\nan organization.\n\nResources lower in the hierarchy inherit policies such as IAM allow policies and\norganization policies. All access permissions are denied by default, until you\napply allow policies directly to a resource or the resource inherits the allow\npolicies from a higher level in the resource hierarchy.\n\nThe following diagram shows the folders and projects that are deployed by the\nblueprint.\n\nThe following sections describe the folders and projects in the diagram.\n\nFolders\n-------\n\nThe blueprint uses\n[folders](/resource-manager/docs/cloud-platform-resource-hierarchy#folders)\nto group projects based on their environment. This logical grouping is used to\napply configurations like allow policies and organization policies at the folder\nlevel and then all resources within the folder inherit the policies. The\nfollowing table describes the folders that are part of the blueprint.\n\nProjects\n--------\n\nThe blueprint uses\n[projects](/resource-manager/docs/cloud-platform-resource-hierarchy#projects)\nto group individual resources based on their functionality and intended\nboundaries for access control. This following table describes the projects that\nare included in the blueprint.\n\nGovernance for resource ownership\n---------------------------------\n\nWe recommend that you apply labels consistently to your projects to assist with\ngovernance and cost allocation. The following table describes the project labels\nthat are added to each project for governance in the blueprint.\n\nGoogle might occasionally send important notifications such as account\nsuspensions or updates to product terms. The blueprint uses\n[Essential Contacts](/resource-manager/docs/managing-notification-contacts)\nto send those notifications to the groups that you configure during deployment.\nEssential Contacts is configured at the organization node and inherited\nby all projects in the organization. We recommend that you review these groups\nand ensure that emails are monitored reliably.\n\nEssential Contacts is used for a different purpose than the\n`primarycontact` and `secondarycontact` fields that are configured in project\nlabels. The contacts in project labels are intended for internal governance. For\nexample, if you identify non-compliant resources in a workload project and need\nto contact the owners, you could use the `primarycontact` field to find the\nperson or team responsible for that workload.\n\nWhat's next\n-----------\n\n- Read about [networking](/architecture/blueprints/security-foundations/networking) (next document in this series)."]]