Skip to main content
Open Planning → Customers (/planning/customers) to search and maintain canonical customer records. Customer reads require customers:read.
Customers (dark)Customers (light)

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.
  • 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, Client health, and Knowledge.