Prepare and test your skills

Prepare and test your skills

Defining initial administrative roles and responsibilities means assigning a small set of Identity and Access Management (IAM) roles that control a new Google Cloud Organization resource (opens in a new tab). The Organization resource is the root node of the resource hierarchy that groups all projects, folders, and billing accounts for centralized policy inheritance and access control. Secure setup depends on keeping three authorities separate: the domain-level Super administrator, the cloud-level Organization Administrator, and billing administrators.
The Super administrator is the domain-level administrator in Google Workspace or Cloud Identity who creates the Organization resource and starts cloud administration. By default, the Super administrator account that creates the organization is automatically assigned the Organization Administrator role. To maintain separation of duties, the Super administrator should delegate that cloud role to a different user or group, which is often necessary because identity management and cloud management are handled by different departments.
In the context of Organization setup, the Super administrator has three core responsibilities:
The Super administrator controls identity recovery while the Organization Administrator controls day-to-day cloud resources, so the two roles sit on opposite sides of a duty boundary. Having more than one Super administrator is recommended so the organization is not locked out if one account becomes unavailable.
The Organization Administrator is the IAM role (roles/resourcemanager.organizationAdmin) that has full control over one organization, its resources, and its IAM policies. An Organization Administrator can take control of any resource inside the organization, define allow and deny policies, grant roles to other users, and view the structure of the resource hierarchy. The Organization Administrator then delegates critical functions by assigning billing, folder, and project roles to other administrators.
The authority of the Organization Administrator is confined to that single organization as a trust boundary. An Organization Administrator cannot access resources in other organizations unless explicitly granted permission, and no user outside the organization can take control away from that organization's administrator. Following the principle of least privilege, the role does not include permissions to create folders or projects, so an Organization Administrator must assign those additional roles to their own account if they need them.
Billing administration controls who pays for Google Cloud usage by managing Billing accounts (opens in a new tab), payment instruments, and the linking of projects to a billing account. When a billing account is associated with an organization, it becomes a sub-resource of that organization and inherits IAM permissions from the organization. Projects linked to a billing account do not inherit permissions from that billing account, so billing permissions and project permissions remain separate.
The three billing roles most important during initial setup differ by scope and power:
A comparison matrix of the three billing roles, contrasting what each role can do, its scope, and its typical holder: Billing Account Creator brings accounts into the organization, Billing Account Administrator manages them, and Billing Account User links projects for payment.
| Role | What it allows | Typical holder |
|---|---|---|
Billing Account Administrator (roles/billing.admin) | Manage payment methods, configure billing export, view costs, link and unlink projects, and manage other users on the billing account | Person with financial control, such as a business lead or budget owner |
Billing Account Creator (roles/billing.creator) | Create new self-serve billing accounts and migrate existing billing accounts into the organization | Small set of setup administrators |
Billing Account User (roles/billing.user) | Link projects to a specific billing account, but not unlink them, and view costs | Trusted Project Creators who need to make new projects billable |
The table shows a clear dependency: the Billing Account Creator brings accounts into the organization, the Billing Account Administrator manages those accounts, and the Billing Account User connects projects to them for payment. Assigning billing administration to finance or budget owners separates who can spend money from who can configure infrastructure.
Exam tip: The Billing Account Administrator manages an existing billing account, while the Billing Account Creator is needed to create billing accounts and bring existing accounts into the organization.
Delegating permissions is the practice of dividing setup power among different users and groups so no single account holds unnecessary control. Keeping the Super administrator separate from the Organization Administrator establishes separation of duties between identity recovery and day-to-day cloud control. Secure delegation also requires cleaning up broad defaults and building redundancy for recovery.
When an Organization resource is created, all users in the domain are granted Project Creator and Billing Account Creator by default so work can begin immediately. The Organization Administrator should replace these broad grants with designated creators and then remove the domain-wide grants to enforce finer control at the folder or project level. Setting up multiple Organization Administrators and more than one Super administrator prevents accidental lockout and ensures someone can recover access or delegate a new administrator when needed.
Establishing the Organization resource through identity providers means creating the root of the Google Cloud hierarchy by verifying a company domain. The organization resource (opens in a new tab) is the central parent for all folders, projects, and billing accounts in a company. It provides central visibility, ownership of projects, and a single point where IAM roles and organization policies are inherited by every child resource.
A Google Workspace account or Cloud Identity account is a prerequisite for having an organization resource, because the domain is the primary company identity for Google Cloud. To acquire an organization, an administrator signs up for Google Workspace or Cloud Identity, associates it with a company domain, and completes domain ownership verification. The Google Workspace super admin is responsible for that verification and for recovery contact, and each Google Workspace or Cloud Identity account can be associated with exactly one organization resource.
The one-to-one relationship means the identity system and the resource hierarchy stay linked. Users are managed in the domain through the Google Admin Console, while cloud resources are managed under the organization that belongs to that same domain. This link allows managed users in the domain to be recognized across Google Cloud and ensures that projects they create can be tied to the company rather than to an individual account.
The organization resource is automatically provisioned once the identity account and domain exist and a triggering cloud action occurs. No separate create-organization command is needed, and no other resources are created at that moment except the organization node itself. The display name of the organization is generated from the primary domain name, and the organization also records a unique organization ID, creation and last-modified times, and an owner tied to the Google Workspace customer ID.
The timing of provisioning depends on whether projects already exist:
| User status | When the organization is created | Where the first child comes from |
|---|---|---|
| New to Google Cloud, no projects yet | When the user logs in to the Google Cloud console and accepts the terms and conditions | The organization is ready for future projects, folders, and billing accounts |
| Existing Google Cloud user with projects | When the user creates a new project or billing account if no organization exists yet | The new project or billing account becomes a child of the new organization |
In both paths, the flow runs from domain verification to console action to automatic creation of the organization node. The new project or billing account that triggers creation flows directly under the new organization as its child, while any older projects remain where they were until they are moved.
Exam tip: One Google Workspace or Cloud Identity account links to exactly one organization, and one organization links to exactly one domain.
Moving from no organization to a centralized hierarchy is the transition that brings standalone projects under central ownership and policy control. Before an organization exists, projects appear under No organization, where each project stands alone without a central parent. When the organization is provisioned, any projects created earlier stay under No organization, while the newly created project is linked automatically as a child of the organization.
This transition changes ownership and control in two important ways. First, ownership binds the lifecycle of a project to its parent, so projects belong to the organization and remain active and secure if the employee who created them leaves. Second, inheritance provides attachment points for policy, so IAM roles and organization policies applied at the organization flow down to every folder and project and the effective policy is the combination of direct and inherited policies. An administrator moves the older No organization projects into the organization to bring them under central control, and all future projects created under the domain become children of the organization.
Initial access and separation of duties describes how broad starting permissions are narrowed into secure cloud administration. When the organization is created, Google Cloud notifies the Google Workspace or Cloud Identity super administrator accounts, which have broad control over the organization and all resources underneath it. Super administrator accounts should not be used for day-to-day management of Google Cloud because that mixes identity recovery power with routine infrastructure changes.
Instead, the super admin's main duty for Google Cloud is to assign the Organization Administrator IAM role (roles/resourcemanager.organizationAdmin) to appropriate users or groups. To avoid disruption, the initial allow policy grants the Project Creator (roles/resourcemanager.projectCreator) and Billing Account Creator (roles/billing.creator) roles to the entire domain. This lets users continue creating projects and billing accounts as they did before the organization existed, even if they cannot yet see the organization node, until the Organization Administrator actively adopts the organization and enforces more restrictive permissions.
Structuring the resource hierarchy for centralized control means arranging the Organization resource (opens in a new tab), folders, and projects into a single parent-child tree for governance. The hierarchy places the Organization resource at the top as the root, optional Folder resources in the middle for grouping, and Project resources at the base to hold service resources. Every resource except the root has exactly one parent, so each project and folder has a clear lineage for billing, lifecycle, and policy control.
| Level | Position in hierarchy | What it holds |
|---|---|---|
| Organization resource | Root node, requires a Google Workspace or Cloud Identity domain | All folders, projects, and service resources in the company |
| Folder resources | Optional middle layer under the organization, can nest inside other folders | Projects, other folders, or a combination of both |
| Project resource | Base organizing entity under an organization or folder | Service resources such as Compute Engine virtual machines, Cloud Storage buckets, and Pub/Sub topics |
The table shows how control narrows downward: the organization parents everything, folders subdivide it, and projects contain the workloads that actually consume services.
The Organization resource represents a company or entity and serves as the parent to all folder and project resources beneath it. A Google Workspace or Cloud Identity account is a prerequisite for an organization, and each such account is associated with exactly one organization tied to exactly one domain. When the organization is created, the Workspace super admin assigns the Organization Administrator role in IAM to separate day-to-day cloud administration from domain administration.
The organization provides centralized ownership and visibility over every child resource. Projects belong to the organization rather than to the employee who created them, so projects remain active and secure when an employee leaves. Organization administrators can view and manage all projects in the company, which prevents shadow projects and rogue administrators.
Folder resources are an optional grouping mechanism between the organization and projects, and an organization is required to use them. A folder can contain projects, other folders, or both, while each folder or project has exactly one parent. Folders function as sub-organizations that can model departments, teams, applications, or environments such as non-production and production.
Folders provide isolation boundaries and delegation points for administration. A department head can receive full ownership over only that department's folder, so users in one department can access and create resources only within their branch. When planning nested folders, three limits keep the hierarchy navigable:
These limits still allow flexible separation of regulated workloads, shared infrastructure, and customer-facing systems while keeping delegation paths clear from the organization through parent folders to child folders and projects.
The Project resource (opens in a new tab) is the fundamental organizing entity that is required to use Google Cloud. Organization and folder resources can contain multiple projects, but any given service resource exists in only one project. Projects are the basis for enabling services and APIs, managing billing, adding collaborators, and managing permissions.
A project is identified by a unique project ID and an automatically assigned, read-only project number that must be supplied with most resource requests. Each project also has a mutable display name, a lifecycle state such as ACTIVE or DELETE_REQUESTED, and labels for filtering and cost tracking. Because the project binds service resources to its parent folder and organization, moving or governing the project moves or governs everything inside it.
Inheritance in the resource hierarchy means that allow, deny, and organization policies attached at a higher node flow down to every child below it. Identity and Access Management (IAM) roles and organization policy constraints can be set on the organization, a folder, or a project, and the effective policy at any node is the combination of policies applied directly to that node plus policies inherited from its ancestors. This reduces manual configuration because one grant at a high level applies consistently to all descendants.
Central teams use this flow to enforce consistent governance with minimal effort. For example, granting the Network Admin role at the organization level lets the networking team manage networks in every project in the company, while granting Compute Instance Admin on a single folder grants it for only the projects in that folder. Ownership follows the same path, so lifecycle and access control stay with the parent organization or folder rather than with individual creators.
Exam tip: The effective policy at any project or folder equals its directly attached policies plus all policies inherited from its parent folder chain up to the organization.
The Super administrator is the domain-level administrator in Google Workspace or Cloud Identity who creates the Organization resource and assigns the Organization Administrator role, while the Organization Administrator is the Identity and Access Management (IAM) role with full control over one organization, its resources, and its IAM policies. The Super administrator handles identity recovery and the lifecycle of the identity account and Organization resource, while the Organization Administrator handles day-to-day cloud control, can take control of any resource inside the organization, and delegates billing, folder, and project roles to other administrators.
The Billing Account Administrator manages an existing billing account, the Billing Account Creator creates new self-serve billing accounts and migrates existing accounts into the organization, and the Billing Account User links projects to a specific billing account. The Administrator can manage payment methods, configure billing export, view costs, link and unlink projects, and manage other users, while the User can link projects but cannot unlink them and can view costs.
The Organization resource is automatically provisioned after a Google Workspace or Cloud Identity account is associated with a company domain and domain ownership is verified, once the user logs in to the Google Cloud console and accepts the terms and conditions or creates a new project or billing account. No separate create-organization command is needed, the display name is generated from the primary domain name, and each identity account is associated with exactly one organization tied to exactly one domain.
Allow, deny, and organization policies attached at a higher node flow down to every child below it, so the effective policy at any folder or project is the combination of directly attached policies plus all policies inherited from its ancestors up to the organization. Every folder or project has exactly one parent, folders are optional and can nest up to 10 levels deep with no more than 300 direct child folders per parent, and a grant at the organization level applies consistently to all descendant projects while a folder-level grant applies only to projects in that folder.
Your company currently has several development teams managing standalone Google Cloud projects using individual, unmanaged Google accounts with no centralized administrative oversight.
Your management team wants to transition from this unorganized state to a centralized resource hierarchy rooted under the corporate domain name (example.com). The company does not require email or office productivity tools (such as Gmail or Google Drive).
What should you do to establish the Google Cloud Organization resource?
Sign up for Cloud Identity with your corporate domain, verify domain ownership, and use the automatically provisioned Organization resource.
Create a top-level Folder in the Google Cloud console and move all existing projects under it.
Use the Cloud Resource Manager API to execute an organization creation request using a project service account.
Link all standalone projects to a single shared Cloud Billing account to automatically generate the Organization resource.
Last updated