> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/project/details.md).

# Edit project details

Change the current project's name, job identifier, production supervisors and description.

Use the **Your Project** page to change the name and details of the project you're working on. Open it from **Project > Details** in the sidebar, which shows it to Owners and Super Admins.

The page edits the project selected in the project menu. To edit a different project, switch to it first, as described in [Switch projects and companies](/getting-started/switch-projects.md).

## Update the details

1. Go to **Project > Details**.
2. Change any of these fields:
   * **Project Name**: required, up to 100 characters.
   * **Job Identifier**: the project's job number. It starts every PO number.
   * **Production Supervisor** and **Asst. Production Supervisor**: the names shown on PO topsheets.
   * **Description**: up to 1,000 characters.
3. Select **Update**.

When the changes are saved, you see "Project updated successfully". If the save doesn't go through, you see "Failed to save project. Try again."

**Update** stays greyed out while a field has a problem, and the field says what's wrong under it:

* "Input is required": the **Project Name** is empty.
* "Input is invalid": the **Project Name** is only spaces.
* "Input is too long": the **Project Name** is over 100 characters, or the **Description** is over 1,000.

Spaces at the start or end of the project name are removed when you save.

## How the job identifier is used

A PO number is the **Job Identifier**, a hyphen and the PO's four-digit number, such as 1234-0001. If the project has no Job Identifier, PO numbers are just the four digits, such as 0001.

The Job Identifier and both production supervisor names also appear on POs. A PO's **Topsheet Info** tab shows them as **Job #**, **Production Supervisor** and **Asst. Production Supervisor**, and the exported PO topsheet shows them as **Job Number**, **Production Supervisor** and **Asst. Production Supervisor**. To find a PO, see [Work on a purchase order](/project/vendors-and-pos/purchase-order-details.md).

{% hint style="warning" %}
When you change the Job Identifier, every PO on the project shows the new PO number as soon as you save, and new exports use it. Copies of POs you've already exported or sent keep the old number.
{% endhint %}

## Where related settings live

* **The petty cash Program Total**: if your company uses petty cash, set it on **Project > Petty Cash**. See [Track petty cash](/project/petty-cash.md).
* **People and roles**: on **Project > Team**. See [Manage your team](/project/team.md).
* **New projects**: select **Add new project** at the top of the project menu. See [Add a project](/getting-started/add-project.md).
* **Wrapping a project**: select **Wrap Project** on the Transactions page. See [Wrap a project](/transactions/transactions/wrap-project.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.rollcredits.io/project/details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.