> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/administration/customize-the-term-used-for-projects.md).

# Customize the Term Used for Projects

You can configure an alias for the short and long, singular, and plural forms of the term Project, as displayed in the Clarity LIMS interface.

### Configuration tool & properties

Renaming is achieved by configuring the following properties, using the omxprops-ConfigTool.jar tool at:

```
/opt/gls/clarity/tools/propertytool 
```

#### Properties

* clarity.alias.project.short.singular - The short term for "Project"
* clarity.alias.project.short.plural - The short term for "Projects"
* clarity.alias.project.full.singular - The full term for "Project"
* clarity.alias.project.full.plural - The full term for "Projects"

#### Rules for alias

* clarity.alias.project.short.singular—Maximum of eight characters.
* clarity.alias.project.short.plural—Maximum of nine characters.
* If multiple words are used, capitalize each word (eg, Test Requests).
* Short form singular and plural aliases are truncated to eight characters and nine characters respectively. An ellipsis is used to indicate truncation.


---

# 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://help.bioinsight.illumina.com/clarity-lims/clarity-lims-v6.3-and-lablink-v2.5/administration/customize-the-term-used-for-projects.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.