In this page:
| Table of Contents |
|---|
Related pages:
| Child pages (Children Display) | ||
|---|---|---|
|
Related pages:
| Child pages (Children Display) | ||
|---|---|---|
|
Add New User
| Info |
|---|
Creating Users There are several methods which can be used to create users in the Lucidity System. Each organisation will need to develop internal processes to determine the best option to suit business needs. For more details on these options refer to the Creating Users in Lucidity page in the user guide. |
| Tip |
|---|
Users can be manually added to Lucidity Access from the User page by:
Click 'Add New'
Complete the fields (see table 'Definitions of Fields' below)
The details captured for each user may vary slightly between each system configuration. Fields marked with * are mandatory
Click 'Save'
Definitions of Fields
User Details | Username | Required for users to log into Lucidity. This is the system unique identifier and a pop-up message will appear in the event of a duplicate. A duplicate cannot be reused.  Note: when a user is created via Lucidity HR, the username will automatically be set to FirstnameLastname. Users can then log in using the 'Reset Password' link, provided a notification email is provided. |
|---|---|---|
First Name | Open text field | |
Last Name | Open text field | |
Notification Email | Email address that will be used for system-generated email notifications (for example, in the event of training completion requirements, task related to incidents raised or actions allocated to a user) | |
Password | Change Password | Required for users to log into Lucidity Password requirements can vary dependant on business requirements and system configuration |
Home Organisation Unit | Organisational Details | These fields denote the users designated organisational areas within the business and are utilised in reports as well as well as for permission scoping. These will always match the organisational details in the users Lucidity HR account. There may be several drop-down fields available here, such as Division, Business Unit, Location, Department and Project. Only 1 can be selected for each area (IE - a user cannot be assigned multiple projects) When a user creates a new record in a module (eg - a new issue or form record) the home organisation unit may be automatically pre-populated for them. These automatic selections can be changed by the user as required. |
Home Organisation Unit | Scope all Modules to just this Organisation | Tick to enable system wide scoping to the selected organisation only Refer to the Define User Scoping page in this user guide for more details |
User Group | User Group | Click 'Add' to assign a user to user groups Refer to the User Group page in this user guide for more details |
Profile | Profile | Select the Profile to be added to the user Refer to the Profiles page in this user guide for more details |
Roles | Modules Listed | Used instead of profiles - cannot be used in conjunction with profiles. Recommended only used in rare occasions when profiles do not meet requirements. Select the specific access roles and apply scoping for the various modules Refer to the Assigning Roles and Define User Scoping page in this user guide for more details |
In this page:
| Table of Contents |
|---|
Related pages: