OVERVIEW
This article details key information and details regarding users and organisational hierarchy.
DETAILS
1. Logon Id Field
Fields: Logon Id
Requirement: Mandatory
Description: An Identifier for the user to authenticate against. This can be the user’s email address or another identifer such as their VanGuard Loin.
Example: ABC123bob.dylan@dept.gov.au
2. Alternate Logon Id Field
Fields: Alternate Logon Id
Requirement: Optional
Description: An alternative Login ID that the user can be authenticate against.
Example: ABC123bob.dylan@dept.gov.au
3. Employee Number Field
Fields: Alternate Logon Id
Requirement: Optional
Description: An Employee Number such as an AGS Number.
Example: 123456
4. Position Field
Fields: Position
Requirement: Optional
Description: A position if applicable.
Example: System Administrator
5. First Name Field
Fields: First Name
Requirement: Mandatory
Description: Users first or given name.
Example: Bob
6. Last Name Field
Fields: Last Name
Requirement: Mandatory
Description: Users last name or surname.
Example: Dylan
6. Email Address Field
Fields: Email Address
Requirement: Mandatory
Description: The Users Email Address that will receive email notifications from Lighthouse.
Example: ABC123bob.dylan@dept.gov.au
7. Manager (User Identifier) Field
Fields: Manager (User Identifier)
Requirement: Optional
Description: The Email Address or LogonID of the Users Supervisors so that Lighthouse can establish the relationship.
Example: FGH567tony.stark@dept.gov.au
8. Level Field
Fields: Level
Requirement: Optional
Description: The Users Level within the Organisation, commonly their Classification.
Example: 1APS6
9. Preferred Salutation Field
Fields: Preferred Salutation
Requirement: Optional
Description: The users Salutation.
Example: Dr / Mrs. / Ms.
10. Contact Phone Field
Fields: Contact Phone
Requirement: Optional
Description: An Optional user metadata to be used.
Example: 6292 1122 Ext 123
11. Dashboard Style Field
Fields: Dashboard Style
Requirement: Mandatory
Description:
D = This suggests Lighthouse to use the System Default Dashboard Style for this user, i.e., use the preference setup in the System Settings.
L = This suggests Lighthouse to display this user’s Dashboard in the List View.
T = This suggests Lighthouse to display this user’s Dashboard in the Tile View.
Example: D / L / T
12. Change Dash Style Field
Fields: Change Dash Style
Requirement: Mandatory
Description:
Y = Suggests Lighthouse to allow the user to change their own Dashboard Style, if the user wishes. This appears as a filter icon on the top-right corner of the Dashboard.
N = Suggests Lighthouse that the user cannot change their own Dashboard Style which removes the option from the filter menu located on the top-right corner of the Dashboard.
Example: N / Y
13. Never Email Field
Fields: Never Email
Requirement: Mandatory
Description:
Y = Suggests Lighthouse that this user should never be emailed, commonly used for CEO or Tier 1 Officials within an organisation.
N = Suggests Lighthouse that this user can be emailed.
Example: N
14. Current User Field
Fields: Current User
Requirement: Mandatory
Description:
Y = This means the user is Active
N = This user is Inactive.
Example: N
15. Can Login Field
Fields: Can Login
Requirement: Mandatory
Description:
Y = This user can log into Lighthouse
N = this user cannot log into Lighthouse, Inactive users by default will be changed to N.
Example: Y
15. Mobile Phone Field
Fields: Mobile Phone
Requirement: Optional
Description: A Metadata field that can be used for the User Mobile Number.
Example: 0401 111 222
16. Cost Centre Field
Fields: Cost Centre
Requirement: Optional
Description: The Cost Centre that is associated to that user. This field is optional but if the cost centre is included it is mandatory that it matches a existing cost centre setup in Lighthouse.
Example: 104568
17. Organisation Unit Code – Level 1 Field
Fields: Organisation Unit Code – Level 1
Requirement: Optional/Mandatory
Description: A Unique Identifier for the Organisation Unit.
Example: ORG001
18. Organisation Unit Name – Level 1 Field
Fields: Organisation Unit Name – Level 1
Requirement: Optional/Mandatory
Description: The Org Unit’s Name
Example: Chief Executive
19. Organisation Unit Deactivated Date – Level 1 Field
Fields: Organisation Unit Deactivated Date – Level 1
Requirement: Optional
Description: A date (if applicable) of the Deactivated Date of the Org Unit
Example: 1/01/2001
20. Organisation Unit Legal Entity (Code) – Level 1 Field
Fields: Organisation Unit Legal Entity (Code) – Level 1
Description: A deprecated function that needs to be blank.
21. Organisation Unit Supervisor (User Identifier) – Level 1 Field
Fields: Organisation Unit Supervisor (User Identifier) – Level 1
Requirement: Optional
Description: The Login ID or Email Address of that Organisational Units Supervisors, this allows Lighthouse make the relationship and use permissions where applicable.
Example: ABC123bob.dylan@dept.gov.au
22. Supervisor for Organisation Unit (Code) Field
Fields: Supervisor for Organisation Unit (Code)
Requirement: Optional
Description: Used to associate an Org Unit to the Users, that they supervise. It is a different direction to link a user as a Supervisor than Organisation Unit Supervisor (User Identifier) – Level 1.
Example: ORG001