> For the complete documentation index, see [llms.txt](https://docs.protoboard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.protoboard.xyz/start-here/projects-boards-and-parts.md).

# Projects, boards and parts

How projects, boards and parts relate in Protoboard, and how access and visibility flow from a project to its boards

## Goal

Understand the three building blocks of Protoboard so that sharing, visibility and saving behave the way you expect.

## The short version

* A **board** is one system design: parts on a canvas, harnesses between them, a bill of materials (BOM), and DRC results.
* A **project** is a folder of boards. Access you give on a project applies to every board in it, including boards added later.
* A **part** is a real component placed on a board. Its definition (the **part template**) comes from the open ProtoPart library or is one you made.

```mermaid
flowchart LR
  A["Your account"] --> P1["Project: Line-Following Robot<br/>roles: Owner, Editor, Viewer"]
  A --> B0["Board without a project"]
  P1 --> B1["Board: Main controller"]
  P1 --> B2["Board: Sensor test rig"]
  B1 --> X["Parts, harnesses, groups, notes<br/>DRC, BOM, version history"]
  T["Teammate"] -. "invited to project<br/>(sees every board)" .-> P1
  V["Anyone with the link"] -. "view-only board link" .-> B2
```

## Boards

A board holds one system. Everything you design lives on the board:

| On the board         | What it is                                                                       |
| -------------------- | -------------------------------------------------------------------------------- |
| **Parts**            | Components placed on the canvas, each with a nickname and a template             |
| **Harnesses**        | Connections between two parts, carrying an interface link and its function links |
| **Groups and notes** | Coloured frames and sticky notes that organize the canvas                        |
| **Board Identity**   | Description, tags, requirements, tasks and kit restrictions                      |
| **Review comments**  | Notes from you, teammates or ProtoBot in Board Review                            |
| **BOM**              | Quantities, suppliers and prices for every part                                  |
| **Version history**  | Automatic snapshots you can restore                                              |

Boards save to the cloud when you're signed in. A board you create while signed out, or one you import from a file, starts as a local **draft** in your browser until you save it to the cloud. See [Saving, drafts and recovery](/organize/saving-and-drafts.md).

<figure><picture><source srcset="https://3535233690-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHc6ZGiGpKHrs578383AS%2Fuploads%2Fgit-blob-df485512d90198b4f3d698efa407d347a67fe01c%2Fproject-page-boards-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://3535233690-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHc6ZGiGpKHrs578383AS%2Fuploads%2Fgit-blob-aa67941e21499e0e8a97f0c92f1c66ecfef2d384%2Fproject-page-boards-light.png?alt=media" alt="The Line-Following Robot project page listing three boards: Main controller, Chassis wiring v0 and Sensor test rig"></picture><figcaption><p>A project page with three boards.</p></figcaption></figure>

## Projects

A project groups boards and carries their access:

* A board belongs to **one project or none**. Move it with **Move to project** on its card.
* People you invite to a project get that role on **every board** in it. A board's share dialog shows these people as "via" the project.
* You can still share a single board on its own. That person sees only that board.
* Deleting a project doesn't delete its boards. They become boards without a project.

See [Projects](/organize/projects.md) and [Roles and access](/collaborate/roles-and-access.md).

## Visibility

Every project and board is **public** or **private**.

|              | Public                                    | Private                                      |
| ------------ | ----------------------------------------- | -------------------------------------------- |
| Who can view | Anyone with the link; listed in Community | Only people with access, or with a view link |
| Who can edit | Only people with Editor or Owner access   | Same                                         |
| Limit        | Unlimited                                 | Free accounts: 2 private boards              |

A board can't be more public than its project: making a project private makes all its boards private. See [Public, private and view links](/collaborate/visibility-and-links.md).

## Editing

One person edits a board at a time. Everyone else sees the board in **Viewing** mode, which is read only, until they click **Start editing** or **Request control**. See [Edit control](/collaborate/edit-control.md).

## Parts and templates

When you add a part from the Parts Bin, Protoboard copies its definition into the board as a **part template**. Every instance of that part on the board shares the template, so a fix to the template updates them all. A template defines the part's **interfaces** (what it can connect with), **functions** (the individual signals) and **resources** (the physical pins and ports). See [Part status](/parts/part-status.md) and [Edit part templates](/parts/edit-part-templates.md).

## Common failures

<details>

<summary>A teammate can't see a board I made</summary>

The board isn't in the project you shared, or it's in no project. Move it into the shared project, or share the board on its own.

</details>

<details>

<summary>I can't make a board public</summary>

Its project is private. Make the project public first, or move the board to a public project.

</details>

## Related pages

* [Quickstart](/start-here/quickstart-10-minutes.md): create your first project and board
* [Projects](/organize/projects.md): create, rename, archive and delete
* [Roles and access](/collaborate/roles-and-access.md): who can view, edit and manage
* [Glossary](/reference/glossary.md): every term in one place
