> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/users/user-attributes.md).

# User attributes

Attributes store structured facts about a user, such as student number, intake, region, organisation or department.

| Value type        | Suitable example            | Behaviour to expect                       |
| ----------------- | --------------------------- | ----------------------------------------- |
| Text              | External learner ID         | Preserves a free-form value               |
| Number            | Year group or numeric score | Can be validated and treated as a number  |
| Date or date-time | Employment start date       | Stores a consistent calendar value        |
| True or false     | Requires equipment          | Represents a yes/no condition             |
| Single select     | Region                      | Restricts the user to one approved option |
| Multi-select      | Areas of interest           | Allows several approved options           |

Attributes can appear on profiles and tables, be updated through supported bulk and import workflows, and feed filtering, reporting, integrations and Dynamic Content.

Use Attributes for data, not for authority. A value such as **Department: Biology** describes the user; a User group, access policy or Permission controls what they can reach or administer.

{% hint style="info" %}
Define an Attribute centrally before importing it at scale. Keep its name, value type and allowed options stable so that filters and integrations do not have to interpret several versions of the same fact.
{% 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://synap.ac/docs/platform/users/user-attributes.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.