> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/setup-and-configuration/creating_salespeople_records.md).

# Creating Salespeople Records

Create Salesperson/Purchaser records for users, reporting, and access patterns.

Each time you create a new salesperson record, you must also create a salesperson dimension and attach it as a default dimension against the salesperson record.

### Salespeople Dimension

Before you create a salesperson record, you need to create a salesperson dimension code. Navigate to **Dimensions**, select the Salesperson dimension, and go to the **Dimension Values**. Create a new record in here.

### Salespeople Fields

The fields that need to be populated are:

* Code
* Name
* **Salesperson Code** - assign the salesperson dimension code you created in the previous step. If you cannot see the field on the salesperson card, go to **Salesperson - Dimensions** in the ribbon. Enter the salesperson dimension, the relevant dimension value, and set the **Value Posting** to be **Same Code**.

{% hint style="info" %}
If you do not assign the Salesperson dimension code to the salesperson record, the salesperson dimension will not be populated on any sales transactions created.
{% endhint %}


---

# 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://kb.bevica.com/documentation/guides/setup-and-configuration/creating_salespeople_records.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.