## Name the project

When naming your project, it's good practice to compose a name that:

- Incorporates some basic information about the project.
- Won't be confused with that of another project.
- Can represent all the s within the project.

Meaningful names are important. A generic name such as `project-gamma-798`, is
effectively "camouflaged" and won't stand out in a list of other
generically-named projects.

Consider the following guidance when naming your project:

- Use your company name
- Use the type of project or action in the name
- Don't use "test" in the project name

For example, `acme-smarthome` and `acme-lighting` are clear and unique project
names.

## Create the project

A developer project represents one or more integrations.
By sharing a project with the members of their development team, the
owner can allow other users to manage all integrations in the project.

Google Smart Home Ecosystem integrations are managed using the
Google Home Developer Console.

### Create a new project

Go to the Developer Console:

[Go to the Developer Console](https://console.home.google.com)

1. On the **Manage projects** page, click **Create a project**.
2. On the **Get started** page, click **Create project**.
3. Enter the name of your project, which should adhere to [the project naming
   guidelines](https://developers.home.google.com/project/create#name_the_project).
4. Click **Create new project**.

You are redirected back to the **Home** page for the new project.

### Method 2: Import an existing project from the Actions on Google console

## Set log levels

By default, only error logs are saved to Google Cloud for each
integration in your project.

To save all logs to Google Cloud for each integration, select **All
logs** in the **Log level control: Error logs** section.

![Google Home Developer Center project log levels](https://developers.home.google.com/static/project/images/GHDC_log-level.png "Google Home Developer Console project log levels")

This setting applies to *all* integrations in
your project. It can only be overridden for Cloud-to-cloud
integrations. Saving all logs to Google Cloud may incur additional
cost if your log storage space is exceeded.

## Share a developer project

You may add or remove access to a project among the users on your
team using [predefined roles](https://cloud.google.com/iam/docs/roles-overview#predefined).

> [!NOTE]
> **Note:** To add users to a project, you must have the Owner role on the project.

1. On the **Home** page of the Developer Console click
   **Members** , which takes you to the **IAM \& Admin** \> **IAM** page
   on the Google Cloud Console.

   Or, click **Project details** , then click **Manage members in GCP** in the
   **Members** section at the bottom.
2. Make changes as necessary using the Google Cloud Console
   dashboard.

For instructions for how to modify access to a project, refer to the
[Access control for projects with IAM](https://cloud.google.com/resource-manager/docs/access-control-proj).

Once added to the list of users, a user can view the project and any
integrations in the Developer Console.

> [!NOTE]
> **Note:** The system does not proactively notify users added to a project.

According to your organizational setting, you might experience permission errors
when attempting to create developer projects. If so, reach out to your
Google Cloud administrator and request
[Project Creator permissions](https://cloud.google.com/resource-manager/docs/access-control-proj#resourcemanager.projectCreator) for your account.