> This page is for Harness.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# Personalization

> **Warning**
>
> Personalization requires the reasoning engine to run GPT-5. GPT-4.1 is not supported. See the [Reasoning Engine Upgrade Program](/harness/reasoning-engine-upgrade-program) for model versions.

Personalization tailors the assistant's answers to each employee using their user attributes, such as location, role, and department. The engine adds those attributes to what it reads on each turn, so when it summarizes content it found (files, knowledge articles, and so on), it can pick out the parts that apply to that person. This makes answers more relevant and clearer.

Personalization uses only the user attributes your admin maps. It does not learn from conversations or save preferences.

> **Note**
>
> **Limitations**
>
> * Applies only to answers from [Enterprise Search](/ai-assistant/enterprise-search/overview) (knowledge and file search) in the assistant.
> * Attributes tailor the answer built from the content that knowledge and file search return. They can only surface what is written in that content.
> * The engine can rewrite search queries using attribute values.

![](https://files.readme.io/2a75feff50dc81eb58a6b1e45326a8db689689253875fb30fc4e8841d8467be7-CleanShot_2025-10-31_at_14.45.01.png)

## How it works

By default, the assistant uses these **native** attributes from your identity integration:

* Location
* Country code
* Role
* Department

Admins can also configure **custom** attributes. These categories tend to help:

| Category                  | Examples                                                                             | What it helps with in search                                                                                                           |
| ------------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Organization and role** | Job grade, business unit, employee level                                             | Picking the relevant part of the retrieved content (for example, sales vs. engineering topics)                                         |
| **Employment and status** | Salary basis code, years of service, employment type (full-time, intern, contingent) | Specific HR, payroll, and benefits answers ("Your vacation accrual is...") when the retrieved content covers them                      |
| **Location**              | Subsidiary, building, work location (office or remote)                               | Location-specific information such as local holidays, office facilities, and regional policies, when the retrieved content covers them |
| **Device profile**        | Laptop OS (Mac or Windows), MDM status (enrolled or not enrolled)                    | Targeted IT support and the right how-to guide ("Here is the VPN guide for macOS...") when the retrieved content covers it             |

Native and custom attributes are added to the engine's system prompt. When the assistant summarizes retrieved content, it tailors the answer to these attributes.

## Configure it

1. **Map the attributes into the user record.** In **Moveworks Setup** > **User Identity** > **Import Users**, make sure the native and custom attributes you want are mapped. Mapped attributes are used for personalization automatically. See the [User Attribute Reference](/platform-management/user-identity/user-attribute-reference) for the attributes that should be mapped. To use location or another general attribute from a source other than your primary one, override the native attribute.

   ![](https://files.readme.io/87d87066c1f054b8437e97034563f9cc0a33e9e8a6aa39973df91e904ba4ed57-UPDATE-CleanShot_2025-10-14_at_20.33.29.png)

   You can also ingest custom attributes through Content Gateway. See `/users` in the [Data API reference](/api-reference/data-api/list-users).

   ![](https://files.readme.io/92150800a61acb09673225a9f679c95b535fc7bdffb975735cfa64887f2b7f9f-UPLOAD-CleanShot_2025-10-14_at_20.31.41_1.png)

2. **Choose which attributes the assistant sees.** In **Moveworks Setup** > **AI Assistant** > **Advanced Settings** > **User Attribute Personalization**, map the attribute keys you want to friendly names and descriptive labels. Pick the subset that helps personalization most.

   ![](https://files.readme.io/83fa1d75c7f6e8388932ca48c56acacfc57e7e3c8011c612d9fb73000b5a8bcb-CleanShot_2025-11-13_at_09.59.19.png)

3. **Confirm the attributes were ingested.** In **Moveworks Setup** > **Core Platform** > **Imported Users**, check the attribute in the **All Users** view.

## Related

* [Conversation History](/harness/agentic-reasoning-engine/conversation-history): what the assistant carries over within a conversation.
* [What Goes Into a Turn](/harness/agentic-reasoning-engine/how-the-reasoning-engine-works): everything the engine reads before each step.