Redmine

h1. Managing users

{{>toc}}

h2. Users list

The users list shows only the activated users by default. To view all users (activated, registered and locked users), change the status filter to 'all'.

* *Login:* The login of the user.

* *Firstname:* The firstname of the user.

* *Lastname:* The lastname of the user.

* *Email:* The email adress of the user.

* *Administrator:* If the icon !/images/true.png! is present, the user is designated as an administrator who has unrestricted access to the application and to all projects.

* *Created:* Indicates the date when this user account has been created.

* *Last connection:* Indicates the date when this user logged into the application the last time.

p=. !user_list.png!

h3. User status

Depending on the global configuration users can have several statuses:

* *active*

** This icon !/images/locked.png! means that the account is activated. A user having an activated account can log in and access the application.

* *locked*

** This icon !/images/unlock.png! means that the account is locked. A user having a locked account cannot log in and access the application.

* *registered*

** This icon !/images/unlock.png! can also mean that the account is registered but _not activated_. A user having a registered account cannot log in and access the application.

This status is used for [[RedmineSettings#Self-registration|self-registered]] users which first needs to be activated by either visiting a link provided by email themselves or by an Redmine administrator manually.

The Lock/Unlock buttons let you *lock/unlock* the activated users and the Activate button let you *activate* registered users.

h2. User authentication

Users are authenticated by _login_ and _password_. These tokens can be managed by Redmine directly, by an external LDAP or OpenId server, or by Redmine plugins which allow for instance to reuse an already available Apache authentication.

h2. Adding or editing a User

_A user designated as an administrator has unrestricted access to the application and to all the projects._

TODO

<pre>

## This statement is important ##

In editing mode, leave the Password field blank in order to keep the user's password unchanged.

## Improve this list to match global descriptions and to prevent duplication ##

 * Login - The User's Login account.

 * Firstname  - The User's First name. 

 * Lastname - The User's Last name

 * Email - A user's email address which receive a mail sended by project.

 * Language - Set a User's mother language.

 * Administrator - If checked this property, this account has unrestriced access to the application and to all projects.

 * Authentication 

 ** Password  - New password

 ** Confirmation - Confirm a new password

 * Send account information to the user - If checked this property, send a Account information to the user's email address when changed user's information by administrator.

</pre>

h2. Deleting a User

TODO

<pre>

Document the fact that users cannot be deleted from the Redmine system and link to references.

I think it's worth describing in more detail what the Lock function does.  This was important to me,

when faced with the task of blocking a former employee from our system.  Here's what I've found so far:

* Prevents the user from logging in to Redmine.

* Excludes the user from various user lists (assignee, Feedback giver, watcher, etc.).

* Omits the user's name from the project overview's list of all project members.

* Prevents the user from receiving Redmine emails.  (http://www.redmine.org/issues/5773)

</pre>