> ## 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.

# Customers

> Maintain the customer directory used by projects, planning, knowledge, and delivery views.

Open **Planning → Customers** (`/planning/customers`) to search and maintain canonical customer records. Customer reads require `customers:read`.

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

Customers — Forge Console at `/planning/customers`

## What you can do

* Search the customer directory and open a customer's details, projects and identifiers. See [Find or update a customer](#find-or-update-a-customer).
* Create, edit, archive or restore a customer when your role permits it.
* Read an Organization Customer's knowledge from its overview card.

## Find or update a customer

1. Search the directory and load more results when offered.
2. Open the customer to inspect its details, projects, identifiers, and planning context.
3. Use the page actions to create, edit, archive, or restore when your role permits them.

The expected result is one canonical customer record reused by customer selectors across Planning. Active Organization Customers also have a linked Forge Organization for planning attribution; they are not inserted into the internal workforce hierarchy.

## See an organization's knowledge

The overview of a customer with an active Forge Organization shows an **Organization knowledge**
card: how many active entries the organization's knowledge holds (it stops counting at 200 and shows
"200+"), its top cases, and **Browse all**, which opens the Knowledge Base filtered to that
organization. The card needs `knowledge:read`, and the organization's knowledge reads only for
someone who may act for that organization; otherwise the card says you can't read it. Opening a
case or **Browse all** acts for the organization, as choosing it under **Acting for** does: the
selection is recorded first, and a refused one says why and shows nothing. A customer without an
active Forge Organization shows no card.

## Key state to watch

* **"200+"** — the knowledge card stops counting at 200 active entries.
* **"You can't read it"** — you lack `knowledge:read` at that organization's own unit or at platform scope.
* **A closed editor** — losing access closes the form; regain access before editing again.

## Troubleshoot

* **Directory access is denied:** request `customers:read` at the intended scope.
* **A form closes after access changes:** access loss intentionally closes the editor; regain access before editing again.
* **Customer knowledge is absent:** that link separately requires `knowledge:read` at the governing root organization.
* **Organization knowledge says you can't read it:** acting for an organization needs `knowledge:read` at that organization's own unit or at platform scope; a grant at Gloo's root does not reach it.

See [Projects](https://docs.gloo.com/forge/console/planning/projects.md), [Client health](https://docs.gloo.com/forge/console/planning/client-health.md), and [Knowledge](https://docs.gloo.com/forge/console/knowledge.md).

## Related surfaces

* [Client health](https://docs.gloo.com/forge/console/planning/client-health.md): each client's open tickets, most urgent first.
* [Projects](https://docs.gloo.com/forge/console/planning/projects.md): the projects linked to a customer.
* [Customer support knowledge](https://docs.gloo.com/forge/console/knowledge/artifacts#customer-support-knowledge): the knowledge scoped to one customer.


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