> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/administration/modifier-collaborateur.md).

# Edit an employee

Go to the'**Administration** section **Employees** (`/administration/users`).

Click on the collaborator’s name you want to edit to access their profile, then click the button **Edit**.

## Editable fields

You can change the following information:

* **First name** and **Last name**
* **Email address**
* **Job title** (job title)
* **Department** (selection among existing departments)
* **Site** (selection among existing sites)
* **Phone**
* **Role** : administrator or member

**Note** : modify the **service** or the **site** of a collaborator may change their communities: they may be automatically added to or removed from dynamic communities according to their rules. If you had given them the administrator role on a community they leave, that role is removed at the same time.

## Save changes

After modifying the desired fields, click the button **Save** to save the changes.


---

# 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://help.steeple.com/en/administration/modifier-collaborateur.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.