> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/projects/project-overview-dashboard.md).

# Project Overview Dashboard

A walk-through of the project overview dashboard

When you select a project, the Project Overview dashboard is shown.  The dashboard has two sections:  **Projects Steps** and **Recent Activities**.

<figure><img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2FT8DKNbM3olB84IZfPTxu%2FScreenshot%202026-06-30%20at%205.32.21%E2%80%AFPM.png?alt=media&amp;token=a84989ae-c094-4d78-a505-6cb626da00e0" alt=""><figcaption></figcaption></figure>

## Project Steps

Project steps show the six major components of a typical project: Project Definition, Collaborator, Data Schemas, Datasets, Code Objects, and Code Runs.  As a component's project items are completed, the icon turns blue and the text below it is updated with the number of project items completed.  Steps that have not been implemented remain gray.  Note that not all projects have all six steps implemented.  For example, you might have a project that does not have collaborators or a code run.

* **Project Definition:** This step was completed when the project was created.
* **Collaborator:** Indicates whether one or more individuals or organizations were added to the project.  The number in parenthesis below the icon shows the number of collaborators (individuals or organizations) that are part of the project.  Once collaborators are added, team members that have the appropriate permissions can work with collaborators to perform federated actions. &#x20;
* **Data Schemas:** Shows whether there are one or more Data Schemas or structures for the data  to be imported as a cohort into the project. The number in parenthesis below the step icon shows the number of data schemas in the project. &#x20;
* **Datasets:** Indicates whether one or more datasets have been imported into the project.  Datasets are often used for analysis, annotation, or ML model training.  The number in parenthesis below the step icon indicates how many datasets are in the project.
* **Code:**  Shows how many code objects are in the project.  A code object is the basic computational building block of a project.  A Code Object can be as simple as a single line of Python code intended to run on a single input dataset, or as complex as a fully custom pipeline for federated training across multiple sites. The number in parenthesis below the step icon indicates how many code objects are in the project.&#x20;
* **Code Runs:** Indicates how many code runs are in the project.  A code run is the execution of a code object.  Logs and output datasets are produced during this step. The number in parenthesis below the step icon indicates how many code runs are in the project.&#x20;

## Recent Activities

The Recent Activities section shows actions that have been performed within the project. Each item shows what was performed, who performed it, and when the activity happened. This is a great traceability tool.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rhinofcp.com/projects/project-overview-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
