How do I start using a Cloud Project?
Create a Cloud Project in the Account that will own the application and pay for its Cloud usage. A Project groups the application's resources, enabled services, and access policies. Keep its Project ID for later CLI commands and API requests.
The Account remains the tenant and payer. Each Project belongs to one Account and cannot be transferred to another Account.
Before you create a Project
Install the Socra CLI with the Account and Project plugins, then sign in to the intended Account. Project commands use the active Account. If your team already has a Project for this application, use that Project instead of creating another one.
List the Projects you can see:
socra project list --limit 100
The default page contains up to 20 rows. A larger page can still be incomplete. If the command prints a continuation cursor, replace CURSOR below with that value and continue until no further page remains:
socra project list --limit 100 --after CURSOR
If you already know the Project ID, replace PROJECT_ID with its proj_… value and retrieve it directly:
socra project get PROJECT_ID
A missing result does not establish that the Project was deleted. Check the active Account, all list pages, and your access before creating a replacement.
Create the Project
Choose a Project slug for the application. Replace PROJECT_SLUG with that value:
socra project create PROJECT_SLUG
A successful response contains the Project ID, slug, and status. Save the ID and retrieve the new Project with socra project get PROJECT_ID to confirm the intended resource.
Project creation saves the Project before registration finishes in IAM and Service Usage. If the next setup step reports that the consumer Project is unknown or not ready, keep the returned ID and retry that step with the same Project. If the error persists, give the Project administrator the ID and exact error. Do not create a duplicate Project to resolve a registration delay.
Creating a Project gives you a place to manage Cloud resources. Enable the services the application needs through Service Usage, then create those services' resources in the Project. Service enablement and permission to use a service are separate controls.
Project management is also available through the Cloud Console. The Projects reference describes the CLI and API surfaces.