Differences

This shows you the differences between two versions of the page.

--- user_management [2019/01/05 14:48] – lucy
+++ user_management [2019/08/02 12:07] – lucy
@@ Line 1: / Line 1: @@
-===== Introduction =====
+====== Introduction ======
-LUCY offers a role-based access control (RBAC), restricting system access to authorized users. The permissions to perform certain operations are assigned to specific roles within the user settings. Members or staff (or other system users) are assigned particular roles, and through those role assignments acquire the computer permissions to perform particular LUCY functions.
- ===== Where can you configure the user settings? =====
+LUCY offers a role-based access control (RBAC), restricting system access to authorized users. The permissions to perform certain operations are assigned to specific roles within the user settings. Members or staff (or other system users) are assigned particular roles, and through that role, assignments acquire the computer permissions to perform particular LUCY functions.
+===== Where can you configure the user settings? =====
 In LUCY  you will find the user settings under "Settings/Users":
-{{ users_where.png?600 }}
+{{ usr_mng_3.png?600 }}
 ===== Is there a limitation on how many users can access LUCY? =====
 No. You have the ability to create as many LUCY users that can access the web console as you want.
@@ Line 19: / Line 20: @@
-  * **User**: this user role created by the admin user can be given individual rights for each LUCY feature. The user can later be added to a specific campaign.
+==== User ====
-{{ user_role.png?600 }}
+This user role created by the admin user can be given individual rights for each LUCY feature. The user can later be added to a specific campaign.
-{{ usersettings.png?600 }}
+{{ usr_mng_1.png?600 }}
-  * **Supervisor**: Maintain the overview with access to the campaign specifications.  Communicate directly with the campaign creator (user) to suggest changes and give approval to green light the campaign (in LUCY > 3.1). The supervisor is in the hierarchy above the user. Therefore it is not possible to supervise a system admin. The Supervisor is technically the same as the user account, but you may assign users to the supervisor account and approve/reject their campaigns. Within the settings you can select which users you want to supervise:
+{{ usr_mng_2.png?600 }}
-{{ user_role_s.png?600 }}
+==== Supervisor ====
-You have the ability to define a supervisor who is able to START/STOP the campaign which was created by a user. To do so add an user to a campaign with all permissions selected, add his supervisor to the same campaign with "Campaign start/stop" permission selected. As a result the supervisor will only be able to go into the campaign and approve or reject the start.
+Maintain the overview with access to the campaign specifications.  Communicate directly with the campaign creator (user) to suggest changes and give approval to green light the campaign. The supervisor is in the hierarchy above the user. Therefore it is not possible to supervise a system admin. The Supervisor is technically the same as the user account, but you may assign users to the supervisor account and approve/reject their campaigns. Within the settings you can select which users you want to supervise:
-  * **Administrators**: The LUCY admin can save all settings within LUCY and run the campaign. This is the user that you need to perform your awareness campaigns. You cannot seggragate administrators in a way, that an admin A doesnt see the clients from an admin B. This can only be done in the LUCY SaaS edition.
+{{ usr_mng_4.png?600 }}
-  * **View Only Users**: The View Only User can only see certain statistics of the campaign. This user cannot start/stop a campaign. The user also has no rights in viewing or changing any of the campaign settings. First, you need to create a client name. The client name is always associated with a campaign. Then you can associate that user with the client. As a result the View Only User will only see all the campaigns which belong to that specific client.
-{{ view_user.png?600 }}
+You have the ability to define a supervisor who is able to START/STOP the campaign which was created by a user. To do so add a user to a campaign with all permissions selected, add his supervisor to the same campaign with "Campaign start/stop" permission selected. As a result, the supervisor will only be able to go into the campaign and approve or reject the start.
+==== Administrators ====
+The LUCY admin can save all settings within LUCY and run the campaign. This is the user that you need to perform your awareness campaigns. You cannot segregate administrators in a way, that an admin A doesn't see the clients from an admin B. This can only be done in the LUCY SaaS edition.
+==== View Only Users ====
+The View Only User can only see certain statistics of the campaign. This user cannot start/stop a campaign. The user also has no rights in viewing or changing any of the campaign settings. First, you need to create a client name. The client name is always associated with a campaign. Then you can associate that user with the client. As a result, the View Only User will only see all the campaigns which belong to that specific client.
+{{ usr_mng_5.png?600 }}
 Please make sure you also add the view only user to the specific campaign:
-{{ view_only_addu.png?600 }}
+{{ usr_mng_6.png?600 }}
+===== How to convert users to LDAP-based? =====
+Lucy has the ability to convert the account to LDAP-based, so existing user can be logged in through LDAP. You can convert multiple accounts at once by selecting the necessary users and clicking the button "Convert to LDAP-based":
+{{:convert_ldap.png?600|}}
+//Note:// Lucy admin should configure the connection to Active Directory service to be able to use this feature. Please find more information about LDAP Integration [[ldap_integration|here]].
 ===== Can I enforce a password policy or strong authentication? =====
-In LUCY < 3.1 there is no option for strong authentication or minimal password complexity. Therefore it is the responsibility of the administrative user to choose secure passwords:
+Yes. It is possible to adjust password policy in the advanced settings.
+Please find more [[password_policies_login_protection_strong_authentication|here]].
+===== Can I authenticate administrative users via SSO? =====
+Yes. It is possible using the AD Federation service and authenticate the users automatically. See [[sso_authentication|chapter SSO.]]
+===== How to set up a multitenant capable administration =====
+To set up a multitenant capable administration, you first need an administrator account. From there you can set up the appropriate users and rights. Here are two use cases and the corresponding configuration:
+**Use case 1**: You create a campaign for your customer, but want to give your customer access to the statistics within the campaign. It must be ensured that the customer only sees his own data and cannot intervene in the campaign configuration.
+{{ rolebased_acces_view.png?600 }}
+**Solution use case 1:** You create a view-only account (1) in "settings/users" and assign this account to your customer. As soon as you create a campaign, you will be asked to enter the customer of the campaign (2). The customer can be yourself, an organizational unit or a third party. Next, you should add the user to the campaign (3). You can then assign the rights to view the statistics to the user (4).
+**Use case 2:** You have a customer who wants to create their own campaigns. However, the customer should only have access to his statistics and not see other customers.
-  * Passwords should have at least eight characters.
+{{ rolebased_acces_view2.png?600 }}
-  * Passwords can’t contain the user name or parts of the user’s full name, such as his first name.
-  * Passwords must use at least three of the four available character types: lowercase letters, uppercase letters, numbers, and symbols.
+**Solution use case 2:** You create an account with the status "user" in "settings/users". Give the user only the right "Create/delete campaign" (1). As soon as the customer logs in, he can then create his campaign and see only the data of the campaigns he created himself (regardless of the assignment of the customer). He wont have acccess to any other menu item (2). However, there are areas where this limited administrator has access to possibly sensitive data of other customers. Examples are custom created templates that may contain customer-related information. But also all recipient groups created on the system can be seen by this customer when assigning recipients.