# Project naming rules

#### Rule for naming a project <a href="#projectnamingrules-rulefornamingaproject" id="projectnamingrules-rulefornamingaproject"></a>

The following rules apply to naming a project in vStorage:

* The project name must be between 1 (minimum) and 40 (maximum) characters long.
* The project name can only include uppercase letters, lowercase letters (a-z, A-Z), numbers (0-9), dots (.), spaces ( ), underscores (\_), hyphens (-), and the @ symbol.
* The project name should not contain sensitive information (such as IP addresses, account names, login passwords, etc.).
* The project name must be unique within a GreenNode account, either within or outside a region, until the project is deleted. We recommend using the name of your business project or product as the name for the project stored in vStorage.

#### Examples <a href="#projectnamingrules-examples" id="projectnamingrules-examples"></a>

* The following examples of project names are valid and adhere to the suggested naming rules:\\
  * project du an 1
  * du-an-nam-2022
  * ...
* The following examples of project names are valid but not recommended for use:\\
  * [docexamplewebsite.com](http://docexamplewebsite.com/)
  * [www.docexamplewebsite.com](http://www.docexamplewebsite.com/)
  * ...
* The following examples of project names are invalid:\\
  * Du an dat hieu qua 80 % (chứa ký tự %)
  * project\_1/2022 (chứa ký tự /)
  * ...


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vngcloud.vn/vng-cloud-document/vstorage/object-storage/vstorage-hcm03/features-of-vstorage/working-with-projects/project-naming-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.