birthe
5 years ago
parent
fd2dd65ca7
commit
164d82fa76
|
After Width: | Height: | Size: 142 KiB |
|
After Width: | Height: | Size: 142 KiB |
@ -0,0 +1,59 @@ |
||||
--- |
||||
sidebar_navigation: |
||||
title: Settings |
||||
priority: 990 |
||||
description: Authentication settings in OpenProject. |
||||
robots: index, follow |
||||
keywords: authentication settings |
||||
--- |
||||
# Authentication settings |
||||
|
||||
To adapt general system **authentication settings**, navigate to -> *Administration* -> *Authentication* and choose -> *Settings*. |
||||
|
||||
You can adapt the following under the authentication settings: |
||||
|
||||
## General authentication settings |
||||
|
||||
1. Select if the **authentication is required** to access OpenProject. |
||||
|
||||
2. Select an option for **self-registration**. Self-registration can either be **disabled**, or it can be allowed with the following criteria: |
||||
|
||||
a) **Account activation by email** means the user receives an email and needs to confirm the activation. |
||||
|
||||
b) **Manual account activatio**n means that a system administrator needs to manually activate the newly registered user. |
||||
|
||||
c) **Automatic account activation** means that a newly registered user will automatically be active. |
||||
|
||||
3. Define if the **email address should be used as login** name. |
||||
|
||||
4. Define after how many days the **activation email sent to new users will expire**. Afterwards, you will have the possibility to [re-send the activation email](../../users-permissions/users/#resend-user-invitation-via-email) via the user settings. |
||||
|
||||
 |
||||
|
||||
## Define a registration footer for registration emails |
||||
|
||||
You can define a footer for your registration emails under -> *Administration* -> *Authentication* -> *Settings*. |
||||
|
||||
1. Choose for which **language** you want to define the registration footer. |
||||
2. Enter a **text for the registration footer**. |
||||
|
||||
 |
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1. Define the minimum password length. |
||||
2. Select what character classes should be part of the password. |
||||
3. Define the minimum number of required character classes. |
||||
4. Define the number of days, after which a password change should be enforced. |
||||
5. Define the number of the most recently used passwords that a user should not be allowed to reuse. |
||||
6. Activate the *Forgot your password.* |
||||
7. Define the number of failed login attempts, after which a user will be temporarily blocked. |
||||
8. Define the duration of the time, for which the user will be blocked after failed login attempts. |
||||
9. Enable or disable the autologin option. This allows a user to remain logged in, even if he/she leaves the site. Is this option is activated, the “Stay signed in” option will appear on the login screen. |
||||
10. Activate the session expiration option. If you select this option, an additional field will open, where you will be able to define the inactivity time duration before the session expiry. |
||||
11. Log user login, name, and mail address for all requests. |
||||
12. Enable REST web service. This activates an API-Interface, which allows communication between external services (for example MS Office) and the instance. |
||||
13. Don’t forget to save your changes. |
||||
|
||||
|
After Width: | Height: | Size: 42 KiB |
|
After Width: | Height: | Size: 100 KiB |
@ -0,0 +1,24 @@ |
||||
--- |
||||
sidebar_navigation: |
||||
title: Custom fields |
||||
priority: |
||||
description: Manage custom fields in a project. |
||||
robots: index, follow |
||||
keywords: custom fields |
||||
--- |
||||
# Manage custom fields in projects |
||||
|
||||
Coming soon! |
||||
|
||||
| Feature | Documentation for | |
||||
| ------- | ----------------- | |
||||
| | | |
||||
| | | |
||||
| | | |
||||
| | | |
||||
| | | |
||||
| | | |
||||
| | | |
||||
| | | |
||||
| | | |
||||
|
||||
Loading…
Reference in new issue