Country or region and language

    Choose your country or region and your language.

    Suggested for you

      All countries and regions

        Choose your character

        It shows in the top bar and on your profile. Change it any time.

        Google Cloud IAM roles and project boundaries

        Identify who makes the request, what operation it needs and where the grant applies. A service name is not a permission review.

        Checked 14 November 2026

        A receipt consumer’s role

        A fictional workload must receive and acknowledge messages. A publisher role names the right service but authorizes a different operation. A role on the operator’s identity also doesn’t grant that workload access. In the IAM binding lesson, inspect the principal, approved role and project. Then change the scenario: if only one subscription is needed, ask whether the project grant is broader than the requirement. Check inherited policy as well as the new binding.

        Identity and enablement

        A service account identifies a workload. Enabling an API makes that service available to the project. Neither step alone grants the workload every required permission.

        The local console saves selected bindings without issuing tokens or evaluating a complete IAM policy. The Google Cloud course connects these decisions with applications and data. Validate effective access, including an excluded resource, before relying on a real grant.

        Sources

        Your Work Gym account

        Save your progress and pick up on another device. Your browser's progress comes with you.

        or

        You can keep practicing without an account.

        Help and feedback

        Ask a question, tell us what is not working, or share an idea. We reply by email.

        What is it about?

        We use it only to reply to you.