> 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/gerer-champs-profil.md). # How do I manage profile fields? ### Manage profile fields Go to the'**Administration** section **Employees**, then go to the page **Directory settings** (`/administration/users/profile-fields`). This page lists all configurable profile fields for your organization. ### Available fields * **Department** : the employee's department (with entry management via modal) * **Location** : the employee's site/location (with entry management via modal) * **Manager** : the line manager * **Job title** : the job title * **Start date** : the date of arrival in the organization ### Enable or disable a field Each field has a **toggle** (switch) to enable or disable it: * **Activated** : the field appears in employee records in administration and in directory profiles * **Disabled** : the field is hidden everywhere ### Make a field mandatory Some fields can be made mandatory when enabled. In that case, the field must be filled in for each employee. --- # 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/gerer-champs-profil.md?ask=&goal= ``` `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.