> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/benutzerverwaltung/benutzer/neuen-benutzer-anlegen.md). # Create and delete users ## Create new user Under Settings -> Users, new users can be created. The wizard guides you through all relevant steps. From the moment of creation, our daily billing starts for the user. ## Delete and restore users {% embed url="" %} ## Master data The master data of an employee essentially consists of name and email address. On the right side you will find functions ... ... to invite the user to the system by email. They will then receive an email to set their password. ... to send the user a forgot-password email. They will then receive an email with a link where they can reset their password for Die Agenturverwaltung.\ If the user is invited, they receive a transactional link by email to a page where they can set their password. {% hint style="info" %} The user should do this themselves so that only they know the password. {% endhint %} Afterwards, they can log in to the system with the email address stored in the system and this password. ... to log in to the system with this user. This option is of course only available to administrators. ... to delete a user and, if necessary, transfer all their responsibilities to their successor. See video above. ## Profile settings In the profile settings, a user can themselves * choose or upload an avatar image * store their email signature for outgoing emails * download a signature graphic template and then upload the graphic with the graphical signature placed on it (it will then be attached to all documents for which this user is responsible. * Turn system notifications via email on and off. * Turn system notifications via Slack on and off, provided a Slack integration is used ## Permissions In the Permissions tab, the user can be assigned to one or more user groups. The permissions for this user are derived from these user groups. The rights from multiple groups are added together. That is, if they are in the "Accounting" group and the "Time tracking" group, they get the rights of both groups. If they are in the administrators group, they have full access to all system data and can also change other permissions themselves. ### Check user permissions To check whether you have assigned the correct permissions to a user, you can go to the system directly as that user in the Master data tab with the button "Log in to the system as this user". You will then only see what this user sees and will only have this user's rights.\ After checking, you can use the avatar at the top right and the button "Back to my user account" to switch the logged-in user back to yourself (with your permissions). ## Time tracking #### Functions In this tab, the time-tracking functions of a user can be defined. These could be, for example, "Art Direction" and "Frontend Development." A person can have several functions. The assigned functions can be sorted. This way, the function selection field in time tracking is prepopulated later. The top function in the list is automatically preselected for this person. #### Activities Activities are usually optional in time tracking, but they can also be made a required field company-wide. An activity in the list of activities assigned to a user can be marked as preselected with the small toggle. That means when the user creates a new time entry, the Activity field is already filled in. --- # 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/einstellungen-1/benutzerverwaltung/benutzer/neuen-benutzer-anlegen.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.