> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/admin-capabilities/overview-2/data-requirements.md).

# Data Requirements

### Overview

This guide explains the essential fields required to set up data in Agentnoon, along with additional custom fields for advanced functionality.

### Three Required Fields

1. **Position ID**: A unique identifier for each position (can be a number or letter, as long as it's unique).
2. **Manager’s Position ID**: Defines reporting relationships by linking a position to its manager.
   * Example: If Ali's Position ID is `1` and Shayan's Position ID is `2`, and Shayan reports to Ali, then Shayan’s **Manager’s Position ID** is `1`.
3. **Job Title**: The title assigned to each position (e.g., CEO, Head of Product) to display on the org chart.

### Custom Fields

* You can import unlimited custom fields, such as:
  * **Department**
  * **Name**
  * **Location**
  * **Employment Status**
  * **Start Dates and End Dates** (useful for tracking hires, planned terminations, and generate accurate forecasts)

### Employee vs. Position Fields

* For advanced functionality (e.g., talent selection, reassigning employees between positions), you need to distinguish between:
  * **Position Fields** (attributes tied to a role, not a specific person)
  * **Employee Fields** (attributes tied to an individual, such as personal details)
* This distinction is managed in the **data import mechanism**, covered in a separate guide.

By setting up these fields correctly, you ensure accurate org visualization and enable more advanced workforce planning capabilities.


---

# 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://docs.agentnoon.com/admin-capabilities/overview-2/data-requirements.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.