> For the complete documentation index, see [llms.txt](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields/fields-overview.md).

# Fields Overview

Use **Fields** to structure and manage data within **Rillet**, giving your organization a flexible way to organize and store information and capture exactly what it needs to track. A well-structured set of Fields also simplifies analysis and reporting, surfacing more actionable insights to support better decision-making.

### Explore Common Use Cases for Fields

Review some typical examples of how Fields can be used:

| Use Case                    | Description                                                                                                                             | Example Setup                                                                                                                                                       |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Organize Data by Department | Track and organize data by department, such as Sales, Marketing, Engineering, and Finance, to analyze spend by team.                    | Add a mandatory Department field with values like Sales, Marketing, and Finance, then use it to report total expenses by department for budget tracking.            |
| Segment Customers           | Segment customers into groups like **Enterprise**, **Growth**, or **SMB** to track contracts and tailor customer strategies by segment. | Create a Customer Segment field, set as mandatory for both customers and contracts, to analyze revenue contribution and target marketing by segment.                |
| Track Projects and Events   | Categorize data by project to monitor costs, progress, or performance for specific initiatives or campaigns.                            | Add a Project field with options like Product Launch 2025, Rebranding, and Customer Outreach, and assign it to expenses and contracts to evaluate project spending. |

Together, these use cases show how a well-structured set of Fields can be applied across departments, customer segments, and projects to support more accurate reporting.

### See Also

To learn more about managing fields in **Rillet**, review these articles:

* [**Create a New Field**](/EjmEP4KZ9BVp9j2ho4Mh/getting-started/set-up-your-books/set-up-fields.md)
* [**Viewing Fields in Income Statement Reporting**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields/viewing-fields-in-reporting/viewing-fields-in-income-statement-reporting.md)
* [**Viewing Fields in MRR/ARR Reporting**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields/viewing-fields-in-reporting/viewing-fields-in-mrr-arr-reporting.md)
* [**Build a Custom Report**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields/viewing-fields-in-reporting/build-a-custom-report.md)
* [**Viewing Fields in ARR/CARR Waterfall Reporting**](/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields/viewing-fields-in-reporting/viewing-fields-in-arr-carr-waterfall-reporting.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rillet.com/EjmEP4KZ9BVp9j2ho4Mh/settings-and-config/custom-fields/fields-overview.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.