The foundational containers.
WHAT A PROJECT CONTAINS
Enabled APIs Resources Credentials and service accounts Permissions An association with a billing account
WHAT TO USE SEPARATE PROJECTS FOR
Different applications
Different environments: development, staging, production
WHY SEPARATE ENVIRONMENTS
So a mistake in development cannot affect production, and so permissions differ.
WHAT AN ORGANISATION IS
A top-level container for projects, tied to a domain.
WHAT IT PROVIDES
Central policy, consistent permissions, and projects that survive individuals.
WHY THAT LAST POINT MATTERS
A project created under a personal account belongs to that person, and is lost with them.
WHAT TO DO ABOUT THAT
Create projects under an organisation, from the start.
WHAT FOLDERS PROVIDE
Grouping projects by team or purpose, with policy applied to the group.
WHAT A BILLING ACCOUNT IS
The payment arrangement, linked to one or more projects.
WHAT TO SEPARATE
Billing administration from project administration.
WHAT TO RECORD
Which projects exist, what each is for, and who owns it.
