A project consists of
Credentials such as API keys are specific to an application rather than to
- a set of applications,
- along with activated APIs,
- Google Cloud resources, and
- the team and billing information associated
with those resources.
However, all applications within a given project use the same
branding information (logo, email address, etc.) on their user consent
screen, as described in
Setting up OAuth 2.0.
Applications within a
project also share
- activated APIs,
- permissions, and
- billing information.
If you create a project, you have owner-level permissions and can grant
owner-level permissions to other project members. Those with owner-level
Only project owners can add and remove other project members and edit
their permission levels. Project owners can share a project with an
email address that represents a group, but every project must have at
least one project member that is an individual, not a group.
To manage project members, do the following:
- Visit the
Google Developers Console
- Select a project, or create a new one.
- In the sidebar on the left, select
- To add a team member or group, select
- You must provide an
email address that is associated with a Google account.
- If the email
address belongs to an individual, an invitation flow is triggered,
and the new project member must accept the invitation before they can
access the project.
- If the email address belongs to a group, the group
is added right away, with no invitation step.
- To change the permission setting for a project member, click the dropdown
box in the Permission column and select a new permission level. The new
permission level is saved automatically.
- To delete a project member, click the trash icon to the right of the
project member's permission setting.
Casiano Rodriguez León