# 2. Create and organise your projects

Once your workspace is set up, you'll want to create projects. Projects house all your canvases, so you'll want to consider how to structure them effectively.

<figure><img src="https://2710183445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTvbqOPoS6WricGDYVJya%2Fuploads%2F8yvtLERRvkV1yEXZq47m%2FScreen%20Shot%202024-05-28%20at%201.13.47%20PM.png?alt=media&#x26;token=4d131e39-bd97-49ec-ad82-47d7a434e6de" alt="" width="151"><figcaption><p>Create a new project within your workspace </p></figcaption></figure>

Here are three aspects to consider:

1. [**Database connections**](#database-connections)
2. [**Naming conventions**](#project-naming-conventions)
3. [**Permissions**](#project-permissions)

## Database connections

<figure><img src="https://2710183445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTvbqOPoS6WricGDYVJya%2Fuploads%2FdroUA1D3jlU5O27ZU3C9%2FScreen%20Shot%202024-05-28%20at%201.16.37%20PM.png?alt=media&#x26;token=f85a2677-d8a1-4889-a078-c85ed364e7d4" alt="" width="375"><figcaption></figcaption></figure>

If you've connected your database, you'll see an option to select which database connection you want associated with each project. All canvases within a project will have access to all databases connected to that project.

Read more about database connections [here](#database-connections).

## Project naming conventions&#x20;

While you may want to have fewer projects when you initially start, keep these naming conventions in mind as you scale your usage in Count.

1. **Per-analyst projects**:
   * Name examples: "Harriet's Playground" or "Harriet's Sandbox"
   * Purpose: Start exploratory work without confusing others. Move it to a shared project when ready to share.
2. **Company-wide projects**:
   * Purpose: For training and MVP canvases.
   * Example: "Company Metric Tree"
3. **Department/team projects**:
   * Name examples: "\[Team Name] Project Name"
   * Purpose: Helps organize projects by team, making it easy to find related projects.

Here's an example of this structure in action:

<figure><img src="https://2710183445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTvbqOPoS6WricGDYVJya%2Fuploads%2FdY7rTX391vZ7QLFRIZjj%2FScreen%20Shot%202024-05-28%20at%201.25.20%20PM.png?alt=media&#x26;token=85ca5c5b-b73a-48aa-bef9-d78fc7847850" alt="" width="563"><figcaption><p>An example of how you can set up your projects with project for individuals, departments, and the whole company</p></figcaption></figure>

## Project permissions

<figure><img src="https://2710183445-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTvbqOPoS6WricGDYVJya%2Fuploads%2FyEt9M89WkUTV10tTvN7Q%2FScreen%20Shot%202024-05-28%20at%201.30.30%20PM.png?alt=media&#x26;token=39fd7ac9-d47d-466e-a0b7-c7a8f34da742" alt=""><figcaption></figcaption></figure>

Permissions can be set at both the project and canvas levels, offering a lot of flexibility and control.

To update your **project-level** permissions:

1. Select the project
2. Click **Manage access** in the right-hand side menu
3. Set the workspace and/or individual permissions

> Only projects a user has access to are visible in the sidebar (except for owners, who have access to all projects/canvases).

Read more about project-level roles and permissions [here](../../../../settings-and-administration/roles-and-permissions#project-roles).

Read more about canvas-level permissions [here](../../../sharing-and-permissions/sharing-permissions).

## FAQ

<details>

<summary>How should I set up projects to restrict access to PII data?</summary>

You'll want to create separate database connections, at least one with PII data and one without.&#x20;

Then create a project that connects to your database connection with PII data, and make sure the permissions for that project are restricted to only the users you want to grant access.

</details>

