# Transfer

A **transfer**, or **mover** event, is a change in a user’s position or attributes that requires access updates.

In this case, the user already exists, but some part of their profile has changed. Common examples include:

* Department change (e.g., Sales → Finance)
* Job role change (e.g., Analyst → Manager)
* Location change
* Promotion or lateral transfer

The transfer event triggers the access update process in OpenIAM.

### Automating the change in access

When users are promoted, reassigned, or demoted, those changes are usually recorded in the HR system and stored on the user object.

OpenIAM can use several fields to detect a position change:

* **Job Code** — metadata-based field
* **Title**
* **Employee type** — metadata-based field
* **Location code**
* **Location name**

You can also update these attributes in a CSV file and run synchronization. When the updated attributes match a business rule, OpenIAM adjusts access based on that rule.

### Position change workflow

To trigger a position change workflow, update the user data so it matches your business rule expression.

You can do this by opening the user record and selecting **Edit**.


---

# Agent Instructions: 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:

```
GET https://docs-beta.openiam.com/automated-user-provisioning/transfer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.