> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Create, filter, and inspect projects, then connect project work to customers and scoped knowledge.

Use **Planning → Projects** (`/planning/projects`) to organize a body of work, its customer attribution, tasks, staffing, and outcomes. Read access requires `projects:read`; creating or changing a project requires `projects:manage` at the applicable scope.

![Projects (light)](https://mintcdn.com/gloo-b243725a/xyq5perq6SLByPBn/forge/images/console/planning/projects-light.png?fit=max\&auto=format\&n=xyq5perq6SLByPBn\&q=85\&s=31b3206494033d3c1e88bea2af6124df)

Projects — Forge Console at `/planning/projects`

## What you can do

* Find a project by status group or customer, and open its detail. See [Find a project](#find-a-project).
* Create a project, internal or attributed to an active customer. See [Create a project](#create-a-project).
* Read a project's tasks, staffing and knowledge on its detail. See [Use the project detail](#use-the-project-detail).
* Retry a failed save without losing the form. See [Recover from a failed save](#recover-from-a-failed-save).

## Find a project

Projects are grouped by **Active**, **Planning**, **On Hold**, **Complete**, and **Archived**. Use **Filter by customer** to narrow the list; **All customers** clears that filter. Choose **Load more projects** when another page is available, then select the project to open its detail.

Customer attribution describes whom the work serves. It does not grant access to that customer's projects or change a project's access boundary.

## Create a project

1. Choose **Create project**.
2. Enter **Project name**. The name is required; whitespace alone does not count.
3. Add an optional **Description**, **Start date**, and **Target date**.
4. Under **Customer**, choose an active customer or keep **Internal (no customer)**.
5. Choose **Create project** and wait for the form to close.
6. Find the new project in the list and open it. Check its name, dates, and customer before adding work.

The current manager becomes the owner. If the customer list is still loading, wait before choosing a customer. Inactive customers are not offered for a new attribution.

For example, an internal project named “Review onboarding knowledge” can group cleanup tasks without attributing them to a customer. A customer delivery project can use the same planning surfaces while recording the customer it serves.

## Use the project detail

The project detail brings together its work and staffing. Use [Tasks](https://docs.gloo.com/forge/console/planning/tasks.md) for individual assignments and [Workstreams](https://docs.gloo.com/forge/console/planning/workstreams.md) for parallel delivery tracks.

The **Knowledge** card shows active entries and recent cases when you have `knowledge:read` in the project's scope. **Browse all** opens Knowledge filtered to the project. Project read access alone does not imply knowledge access; a hidden count is not a zero count.

## Recover from a failed save

A failed mutation leaves the creation form open with its error. Correct invalid input or access, then use **Retry** to retry the last attempted save. Avoid closing the form if you still need its values: **Cancel** and the close control reset it.

| Symptom | Check |
| - | - |
| **No projects for this customer** | Switch to **All customers** and confirm the customer attribution. |
| **No projects yet** | Check your scope and create a project if none is visible. |
| A project is missing | Check every status group and load the remaining pages. |
| Creation is refused | Check `projects:manage` at the intended scope; read access alone is insufficient. |
| Customer is unavailable | The selector offers active customers; verify the customer record in [Customers](https://docs.gloo.com/forge/console/planning/customers.md). |
| Knowledge count is unavailable | Check `knowledge:read` separately from project access. |

## Key state to watch

* **Status group** — **Active**, **Planning**, **On Hold**, **Complete** or **Archived**. A project you can't find may be in another group or on a page not yet loaded.
* **Customer attribution** — records whom the work serves; it never grants access to that customer's projects.
* **A hidden knowledge count** — you lack `knowledge:read` in the project's scope; it is not a zero count.

## Related surfaces

* [Tasks](https://docs.gloo.com/forge/console/planning/tasks.md): the work inside a project.
* [Workstreams](https://docs.gloo.com/forge/console/planning/workstreams.md): parallel delivery tracks.
* [Customers](https://docs.gloo.com/forge/console/planning/customers.md): the customer a project serves.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.