> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/admin-and-settings/taxonomy/areas.md).

# Areas

## Overview

The **Areas** taxonomy page is where you manage all Area records in Birdie Settings.

Areas are one of the core taxonomy types in Birdie. They help you organize broad themes found in customer feedback.

This page centralizes the operational work of managing Areas as taxonomy items. Use it to review your catalog, create new Areas, and organize them into collections.

If you want the conceptual definition of an Area and how it behaves in analysis pages, see [Areas](/core-concepts-and-entities/areas.md).\ <br>

<figure><img src="/files/7w5fMnTZES3zVYclcOdj" alt="" width="563"><figcaption></figcaption></figure>

## Viewing & Searching

The main tab shows the full Area catalog as a list.

Each row includes:

* **Taxonomy ID**, such as `[AR-001]`
* **Area name**, such as `Billing experience`

Use this view to quickly scan your existing taxonomy and confirm naming patterns.

## Creating New Data

Click **New area** to create a new Area.

When creating a new Area:

1. Use a title that represents a theme.\ <br>

   <div data-full-width="true"><figure><img src="/files/nOCRBRPWQBGp7kHEp69y" alt="" width="375"><figcaption></figcaption></figure></div>
2. Define the data filter that represents this theme.\ <br>

   <figure><img src="/files/WrhFLSX7q6u2QrhXYVqr" alt="" width="375"><figcaption></figcaption></figure>
3. Save the record to add it to the catalog.

## Collections Tab

The second tab groups Areas by **Area collection**.\ <br>

<figure><img src="/files/Ohz0ZYI0vFAskB77sWdp" alt="" width="563"><figcaption></figcaption></figure>

This view helps you organize the taxonomy by product, journey, team, market, or another internal structure.

Use collections when you need to:

* keep related Areas together
* make navigation easier
* keep naming and ownership consistent

For broader collection concepts in Birdie, see [Collections](/core-concepts-and-entities/collections.md).

## Best Practices

* Use one Area per broad problem space.
* Keep names short and specific.
* Group Areas into collections that match how your teams work.
* Review duplicates before creating a new Area.

## Related Articles

* [Taxonomy](/admin-and-settings/taxonomy.md)
* [Areas](/core-concepts-and-entities/areas.md)
* [Collections](/core-concepts-and-entities/collections.md)


---

# 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 dynamically by asking a question.

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

```
GET https://ask.birdie.ai/admin-and-settings/taxonomy/areas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.