Google Cloud Storage is available as a service for Google Developers Console projects. You can have many projects and many instances of the Google Cloud Storage service. This page discusses how projects work with the Google Cloud Storage service.
When you interact with the Google Cloud Storage API to create a bucket or list your buckets, you need to provide a project ID. This tells Google Cloud Storage which project you want to create a bucket in or which project to list buckets for. Each project can be identified by their unique project ID. Since it is possible to have multiple projects, this ensures that the request is properly completed in the right project.
The project name is a user-friendly name that you can choose; this is not the ID required to associate a bucket with a project. To find the actual project ID:
- Go to the Google Developers Console.
- Select a project.
- In the project Overview page you can find your project ID
listed under Project number.
To include a project ID with your request, provide the following header:
x-goog-project-id: <project id>
<project id> with your project ID.
Project Members and Permissions
For each project, you can add team members to manage and work on your project as an owner, editor, or viewer. Team membership provides team members with access to buckets and objects in a project as described by their role. For more information about project team members, see Managing projects and applications in the Google Developers Console Help.
Project team members are given the following permissions based on their roles:
- All Project Team Members
All project team members can list buckets within a project.
- Project Editors
All project editors can list, create, and delete buckets.
- Project Owners
All project owners can list, create, and delete buckets, and can also perform administrative tasks like adding and removing team members and changing billing. The project owners group is the owner of all buckets within a project, regardless of who may be the original bucket creator.
When you create a bucket without specifying an ACL, the project-private ACL is applied to the bucket automatically. This ACL provides additional permissions to team members, as described in default bucket ACLs.