Skip to main content
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 (dark)Projects (light)

Projects — Forge Console at /planning/projects

What you can do

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 for individual assignments and Workstreams 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.

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.