> For the complete documentation index, see [llms.txt](https://docs.request.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.request.biz/administrator-guide/data/codes.md). # Codes The **Data > Codes** section allows management of *codes* which are small sets of values that can be used to organize the different entities like templates, tasks, etc.

## Editing a Code Type Click on the tile of choice to edit the values. A new code can be added by clicking on the **Add New** button at the top left of the dialog:

On the left-hand side of the dialog a *New Code* entry appears, and the right-hand pane is changed to display two data entry boxes, **Text** and **Description** where the name (and description) of the new category can be defined:

After making your changes make sure to press the **Apply** button at the top right. To persist your changes press the **Save** button at the bottom of the dialog. ## Supported Code Types Currently the system supports the following code types:

Code Type	Description
Task Categories	Used by the Category property of a Task entity.
Template Categories	Used by the Category property of a Template entity.
Locations	Used by the Location property of several entities.

Note that some code types are represented as a hierarchical tree node list, while others are just a simple flat list. ### Task Categories Clicking the **Task Categories** tile opens the following dialog:

Tasks can then be categorized by the assignee of the task choosing the most appropriate task category from the drop down list:

Note that a task can also have multiple categories. ### Template Categories Templates, when presented to the user, will be grouped by category. Typically, these categories will reflect the type of request being made, perhaps to *order a new product or service*, to *resolve an issue*, *ask a question*, etc.

By default, space.vars.PRODUCT\_NAME comes with the following predefined categories: * *Ask*, * *Change*, * *Inform*, * *Order*, * *Resolve,* * *Schedule*. For most tenants these categories should be sufficient. However, depending on your business requirments, the default categories can easily be added, changed or removed. {% hint style="warning" %} A category can only be deleted if it is not used by any [Templates](/administrator-guide/plans/templates.md) anymore. If a category is being used by one or more Templates the **Delete** button will be disabled. {% endhint %} The template category codes, either default or custom, can be assigned to space.vars.PRODUCT\_NAME [Templates](/administrator-guide/plans/templates.md), either at the time of their definition, or on subsequent editing. The category assignment will determine where the template will be visible to the end user. Note that Template Categories can be structured into a parent/child hierarchy so that the user has a more organized view of the templates available for the various types of requests. Use drag and drop to move nodes to another parent node. See [Editing a Template](/administrator-guide/plans/templates.md#editing-a-template) for more information about assigning a Template Category to a Template. ### Locations Locations can associated with [User Groups](/administrator-guide/security/user-groups.md), and also, if [Microsoft Entra ID (MEID)](/administrator-guide/security/settings/microsoft-entra-id-meid.md) or [Active Directory Federation Services (ADFS)](/administrator-guide/security/settings/active-directory-federation-services-adfs.md) is used for access control, it is possible to control template access through [Roles/External Groups](/administrator-guide/security/roles.md#external-groups-optional) definitions.