user_management []

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 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 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** > **Administrative Users**. Press **+New User** button in order to set up new account.

{{ admusers1.jpg?400 }}

===== User Roles in Lucy =====

There are four types of admin accounts in Lucy:
  - Administrator
  - User
  - View
  - Supervisor

{{:admusers2.jpg?400|}}

**Please note** that there are also End Users accounts in Lucy that come as a part of End User Portal functionality and have no admin rights. This type of accounts is automatically created for the recipients that were assigned to awareness training. More info [[end_user_e-learning_portal|here]]

===== 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. 


===== What are the different user roles? =====

==== Administrator ====

An administrative account with full access and the highest priveleges. An administrator is capable of creating and deleting campaigns, managing all the custom data: recipients, clients, templates and etc. Administrator is also able to manage other administrative users' account data. 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. However, content and recipient data can be managed separately with Users type of administrative account.

==== User ====

This user role can be used in order to separate control of Lucy content based on its affiliation with Clients. Users attributed to specific clients and branches (see below) will have access only to content (campaigns, custom templates, recipient groups) attributed to the same clients and branches.\\
Please make sure to disable the user's permission "Access all Campaigns" to avoid the users from different clients / branches to access the data of one another. Details on this permission are mentioned in the table below in this article.

=== Branches ===

Starting from the 4.8 version [[client_setup#branches|Branches]] functionality is introduced in Lucy.

In order to manage client-related Administrative Users, Lucy allows to create Branches for a [[client_setup|client]] and may represent practically anything - from a tier of management to physical locations, to languages, to organization divisions, to openly defined security levels. 

In case a client has already predefined branches (under the Settings > Clients > Branches - more [[client_setup#branches|here]]) it is possible to assign them to a user.

{{::admusers3.jpg?400|}}

===User permissions===
This user role can be given individual rights for each LUCY feature. After filling out personal data for User account, one may choose various user permissions - that will define which data User will have access to and which Lucy functionality will be available for that account.

**Please Note** - **Clients** and **Branches** attributes access policy.
 In order to separate control of the data related to particular **Clients** and **Branches** users are granted access to the content (templates, recipient groups, campaigns, reports) associated with their **Client** and **Branch** attributes. Also, data that is not associated with any client or branch is available for all users despite the **Clients** and **Branches** attributes access policy. Some of the **User permissions** are affected by this policy. Please refer to the table below in order to check whether **Clients** and **Branches** attributes access policy affects certain permission.

{{::admusers4.jpg?400|}}


=== List of permissions and its description ===
|Access All Campaigns|Right to access campaigns. If you activate this checkbox, the user can access all campaigns, regardless of who created them. This permission overrides **Clients** and **Branches** attributes access policy.|
|Create/Delete Campaigns|Right to Create or Delete campaigns. The user can create and delete campaigns and later access only the campaigns he created himself. Campaigns of other users are not displayed.|
|Save Campaign As Template|Right to save a campaign as a template. A campaign template can be used in the setup process when generating new campaigns. |
|Attack Templates|Access to the list of Attack Templates. Attack templates are predefined emails or websites which can be used for phishing simulations. Affected by **Clients** and **Branches** attributes access policy.|
|Campaign Templates|Access to the list of Campaign templates. Affected by **Clients** and **Branches** attributes access policy.|
|Awareness Templates|Access to the list of Awareness Templates. Awareness templates are used in training campaigns. Affected by **Clients** and **Branches** attributes access policy.|
|File Templates|Access to the list of File Templates. Affected by **Clients** and **Branches** attributes access policy. File Templates are used for [[create_a_phishing_campaign_with_malware_simulations|file based attacks]].|
|Report Templates. Affected by **Clients** and **Branches** attributes access policy.|Access to the [[create_campaign_reports|Report Templates]]|
|Download Templates|Access to the menu of [[download_templates|Templates Downloading]]|
|Clients|Access to the [[client_setup|Clients]] menu|
|Recipients|Access to the list of [[add_mail_recipients|Recipients]]. Recipients are the users that get attacked or trained. Affected by **Clients** and **Branches** attributes access policy.|
|End Users|Access to the list of [[end_user_e-learning_portal|End Users]]|
|User Management|Access to the [[user_management|User Management]]|
|Reputation Levels|Access to the [[assign_multiple_e-learning_templates_based_on_user_reputation_level|Reputation Levels]]|
|SSH Access|Access to the [[remote_ssh_support|SSH Access]] menu|
|SSH Password|Right to reset SSH Password|
|Benchmark Sectors|Access to the [[benchmark|Benchmark Sectors]]|
|License|Right to access License menu|
|Update|Right to [[update_lucy|Update]] LUCY|
|Reboot|Right to [[reboot_lucy|Reboot]] LUCY|
|Domains|Right to access [[domain_configuration|Domains menu]]|
|Register Domains|Right to register a [[domain_configuration|domain]]|
|Dynamic DNS|Access to Dynamic DNS feature.|
|Automated Response Detection|Access to the [[response_detection|Automated Responce Detection]] menu|
|Settings|Access to the [[advanced_settings|Advanced Settings]] including the abillity to customize the [[not_found_pages_404|404]] (not found page)|
|SMS Settings|An ability to set up Short Message Service (SMS) systems to send out text messages. LUCY has a build-in API that will connect to a centralized LUCY gateway when initializing SMS delivery. Please find more information [[smishing|here]]|
|Performance Test|Access to the [[performance_tests|Performance Tests]]|
|Test email|Right to send a [[test_mail|test email]]|
|Spam Test|Access to the [[spam_check|Spam Test]]|
|System Monitoring|Access to the [[system_performance_monitoring|System Monitoring]]|
|System Status Page|Access to the System Status Page. The status page gives a user access to certain [[log_files_in_lucy|logs]]|
|Incident Management|Access to the [[outlook_plugin_phishing_incidents|Incident Management]]|
|Plugin configuration|Right to configure Outlook plugin|
|Incident Management Configuration|Right to configure Incident Management|
|Manual|Access to LUCY manual. This is the WIKI page hosted on th LUCY server|
|Exports|Access to the [[export_campaign_data|exports]]|
|Invoices|Access to the [[invoices_and_balance_refill|Invoices]]. Invoices can be created inside LUCY as a receipt for purchases like domains, sms credits etc.|
|Send Logs|Access to "[[send_us_logs_through_lucy|Send Logs" menu]]. |
|Service Logs|Access to the [[log_files_in_lucy|Service logs]]|
|Changelog|Access to the Changelog|
|Mail Manager|Access to the [[mail_manager|Mail Manager]]|
|Tickets|Access to the Ticket system|


==== Supervisor ====

Maintain the overview with access to the campaign specifications.  Communicate directly with the campaign creator (user) to suggest changes and give approval to greenlight 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:

{{ admusers5.jpg?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.



==== 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** and **Branch**. As a result, the View Only User will only see all the campaigns which belong to that specific client.

{{ admusers6.jpg?600 }}

Please make sure you also add the view only user to the specific campaign:

{{ admusers7.jpg?600 }}


===== Can I enforce a password policy or strong authentication? =====

Yes. It is possible to adjust the 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 to use 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. 

{{ admusers8.jpg?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.

{{ admusers9.jpg?600 }}

**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 won't have access 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.