> 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/getting-started/add-project.md).
# Add a project
Create a new project for your company from the project menu, then invite your team and fill in its details.
Use the **Add Project** page to set up a new project for your company. Open it from **Add new project** at the top of the project menu. The company's Owner sees it, and so do Super Admins on the project they have open.
These are the same fields as the **Project** step of company setup. See [Set up your account and company](/getting-started/set-up-your-account.md).
## Add a project
1. Select the project box in the header, which shows the name of the project you're on. For more on the menu, see [Switch projects and companies](/getting-started/switch-projects.md).
2. Select **Add new project** at the top of the list.
3. In **Project Name**, type the project's name.
4. If you want, fill in **Job Identifier** and **Description**.
5. Select **Save New Project**.
The project is added to the company shown in the project menu. **Save New Project** stays greyed out until **Project Name** is filled in and no field is over its limit.
* **Project Name** is required and can be up to 100 characters. It must be different from every other project name in your company, including wrapped projects and projects you aren't on. If the name is taken, RollCredits shows **Project with this name already exists for this firm. Please use a different name.**
* **Description** can be up to 1,000 characters.
* If you enter a **Job Identifier**, RollCredits uses it with your company name to make the project's email addresses for sending in receipts and invoices, the ones the Transactions page shows, unless another project already has those addresses. The addresses are set only when the project is created, so adding or changing the Job Identifier later doesn't change them.
{% hint style="warning" %}
The page also shows **Production Supervisor** and **Asst. Production Supervisor**, but names typed there aren't saved when the project is created. Add them on **Project > Details** after you save.
{% endhint %}
## After you save
* RollCredits shows **Project created successfully**, switches you to the new project and opens the first page in your sidebar.
* The new project starts with only you and your company's Owner on it. If you aren't the Owner, you're added as a Super Admin.
If saving fails for another reason, RollCredits shows **Failed to save project. Try again.**
## Next steps
* Invite people and set their roles on **Project > Team**. See [Manage your team](/project/team.md).
* Change the project's name or details later on **Project > Details**. See [Edit project details](/project/details.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/getting-started/add-project.md?ask=&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.
