> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/project/project-category.md).

# Project Category

A project category is a way of classifying and grouping projects based on their nature, purpose, or other distinguishing characteristics. This allows businesses to group projects into predefined categories, enabling better tracking, reporting, and analysis of project performance across the organization. By assigning a project category, users can streamline project management processes, ensuring consistency and alignment with organizational goals.

### Key Benefits of Project Category

Categorizing projects into different groups offers several benefits for businesses.

1. **Improved Project Management**: Organizing projects into categories provides better visibility and control over the progress, resource allocation, and interdependencies between various initiatives.
2. **Enhanced Reporting and Analytics**: Categorization allows for more granular reporting, enabling users to generate insights specific to particular project types or categories. This can help in identifying trends, assessing performance, and making informed decisions.
3. **Efficient Resource Allocation**: By categorizing projects, resources can be allocated more effectively based on the specific needs of each category. For instance, high-priority projects may require more resources, while lower-priority ones might need fewer.
4. **Ensure Consistency**: Applying standardized categories across projects ensures consistency in how projects are managed and reported. This is particularly beneficial in large organizations where multiple teams may be working on various projects simultaneously.

### Creating Project Category

Creating a project category in XoroERP is a straightforward process that allows you to efficiently organize and manage your projects. By categorizing projects, you can streamline project management and enhance reporting and analysis capabilities.

{% hint style="info" %}
To create a project category, go to **Menu > Admin > Project > Project Category**
{% endhint %}

In the "Name" field, type the desired name for your project category. This name should reflect the type or purpose of the projects that will be grouped under this category.

Once you have entered the name, click "Save" to create the project category. The new category will now be available for assignment to projects within the system.

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2Fwc1bpRDJXeMer1bPDDQL%2Fimage.png?alt=media&amp;token=b285f633-a997-4172-be43-5eab1b06644f" alt=""><figcaption></figcaption></figure>

### Assigning the Project Category

Once a project category has been created, it can be assigned to any Project/Class in the system. To assign a category to the project, in the Project/Class module, select the category in the "Category" dropdown option and click "Save".

<figure><img src="https://3188343778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkf8DNCjEfcSm64PCPcmf%2Fuploads%2F5g4T8rQfK0TjWdxgTHIT%2Fimage.png?alt=media&amp;token=9e859e8e-a3ef-4f4a-b27a-b307657609ba" alt=""><figcaption></figcaption></figure>


---

# 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://docs.xorosoft.com/xoroerp-1/admin/project/project-category.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.
