> For the complete documentation index, see [llms.txt](https://support.hivo.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.hivo.co/people/organise-people-with-categories.md).

# Organise People with Categories

Group your People Profiles into categories such as Staff, Talent or Client to keep your People list organised.

As your **People** list grows, it can be hard to tell at a glance who is who. With the new **Category** field, you can label each **People Profile** with the group they belong to, for example **Staff**, **Talent**, **Client**

Categories are shared across your organisation, so everyone on your team picks from the same list and your profiles stay consistent.

## 1. Add a Category to a Person

You can set a Category when you create a new person or when you edit an existing one.

The **Category** field suggests categories already used in your organisation as you type, so you don't end up with near-duplicates like *Staff* and *Staff Members*.

* **To reuse a category:** start typing and select it from the suggestions.
* **To create a new category:** type the new name and save. It will then be suggested to everyone in your organisation the next time they set a category.

#### **🔹 When creating a new person:**

* Navigate to **People** -> Click **Add Person**.
* Enter the person's details.
* In the **Category** field, select an existing category or type a new one.
* Then, click **Submit**.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2Fqh5r7WUrRS4fHf2oOjTd%2FGroup%20963.png?alt=media&amp;token=4652ac8d-e003-42f5-83dc-c8972bf340e9" alt=""><figcaption></figcaption></figure>

#### **🔹 When editing an existing person:**

* Navigate to **People** and open the person's profile.
* Click **Edit Details**.
* In the **Category** field, select an existing category or type a new one.
* Save your changes.

👉 Note: Each person can belong to **one category** only.

{% @howdygo/embed url="<https://app.howdygo.com/share/3709d405-7b1f-40fb-b04d-3730e4824f14>" %}

## 2. View a person's Category

The Category is shown in the details panel of the person's profile, alongside their phone number and Recognition status. If no category has been set, the field shows.

<figure><img src="https://2446612760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0sjg5GpIPr5HzBTJYqYe%2Fuploads%2Ft0JINDGomVekjlh6RXUr%2FGroup%20964.png?alt=media&amp;token=48175fca-794e-4f38-bc01-0249dcdee0d1" alt=""><figcaption></figcaption></figure>

## 3. Change or remove a Category

* To **change** a person's category, open **Edit Details** and select or type a different category.
* To **remove** a person's category, open **Edit Details**, clear the **Category** field and save.

Removing a category only clears the label. The person's profile, tagged assets and recognition data are not affected.

👉 **Note: Permissions**

* To add or change a person’s category, you need both the **Can View Recognition Profiles on the People page** and **Can Tag Faces on Assets** permissions.
* Category suggestions only include categories from People Profiles you can view.

If you have any questions, don't hesitate to ask, we're always here to help!


---

# 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://support.hivo.co/people/organise-people-with-categories.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.
