EHR - General Tab

Employee Code

Enter a unique Employee Code.

Person Number

It is important to use the search function to see if this 'Person' is already in the database, e.g. A Past Student or Current Parent.

If you find this 'Person' is already in the database, by linking this new employee record to the existing 'Person', you will not create a duplicate Community 'Person' record.

If this 'Person' is not already in the database, leave this field blank, and the system will create a new 'Person' record in Community.

Teacher Code

This field is not editable here. The link is maintained using TASS.web program Student Admin > Teacher Records > Teacher Information > Teachers.

Once a link between an employee and teacher record has been saved, a 'View' and 'Edit' hyperlink will appear next to this field on the employee record. This provides a quick way to access the linked teacher record from the employee record that you are working on.

Deceased

Yes/No.

Supplier Code

Where this employee is paid from Accounts Payable (e.g. As a contractor) rather than through the Payroll, enter or look up their 'Supplier Code' from Accounts Payable.

Once a link between an employee and supplier record has been saved, a 'View' hyperlink becomes available next to this field on the employee record when it is in view mode. This provides a quick way to access the linked supplier record from the employee record that you are viewing.

*Gender

This will be automatically derived based on the 'Title' entered above (where it can) and can be overridden.

*Title

The options available in this dropdown list have been created by your school using Payroll/HRM > Employee/HR > Setup Information > Employee/HR Setup on the 'Titles' tab.

Choose the appropriate title for this employee.

Editing this field will also update the 'Initials' field on the Community Person Record.

Marital Status

The options available in this drop-down list have been created by your school using Payroll/HRM > Employee/HR > Setup Information > Employee/HR Setup on the 'Marital Status' tab.

Choose the appropriate, marital status for this employee. 

*Initials

Optional.

This field is a maximum of 5 characters.

Editing this field will also update the 'Initials' field on the Community Person Record.

Driver Licence

Driver licence number.

*Surname

A 50 character (maximum) field to enter the Employee's legal surname name.

Editing this field will also update the 'Surname' field on the Community Person Record.

*First Name

A 50 character (maximum) field to enter the Employee's first name.

Editing this field will also update the 'First Name' field on the Community Person Record.

Other Names

Optional.

A 50 character (maximum) field to enter the Employee's additional name's, e.g. Middle Name/s.

Editing this field will also update the 'Other Names' field on the Community Person Record.

*Preferred Name

Optional.

A 50 character (maximum) field to enter the Employee's alternative name.

Editing this field will also update the 'Preferred Name' field on the Community Person Record.

*Name Suffixes

Optional.

A 30 character (maximum) field to enter the Employee's name suffixes, e.g. B.Com CPA.

Editing this field will also update the 'Name Suffixes' field on the Community Person Record.

The name suffixes entered here can be printed on PD Certificates.

Start Date

The date that the employee started at the school. 

Termination Date

This will flag this employee as 'Terminated' for lookups and listings.

It is also used by the system to process the termination of an employee.  

For further information, refer to: How to Terminate an Employee(s).

*Reason for Termination

When a Termination Date is entered this feild will become active.

Select the Reason for Termination when applicable.

Employment Status

Casual, Part Time or Full time. 

Position Text

A 20 character (maximum) field to describe the employee's position, e.g. Head of Department.

This field should not be confused with the 'Position Code' field on the 'Payroll Details' tab.  The 'Position Code' field is used by the system to determine the employee's rate of pay. 

Previous Payroll ID

The ID from a Previous Payroll System if applicable.

Kiosk Password

Non-teaching employees can be given access to the Staff Kiosk portal. Enter the password that they will be given for their initial access to Staff Kiosk here.

The employee will also have to be added into an appropriate Staff Kiosk 'User Role' in TASS.web program System Admin > Users > Portal Security Permissions.

Click the 'Login History' link to display a list of this employee's Staff Kiosk login history. The popup will display the last 30 logins. Use the 'Print All' button to generate a listing of this employee's entire login history.

Click the ‘Ghost Logon' link to log into Staff Kiosk as this Employee. 

The permissions that have been given to the selected Employee will apply to you during the Staff Kiosk session. This can be valuable when trialing or implementing Staff Kiosk programs and settings, allowing you to check functionality prior to rolling out to staff. It will also be helpful when assisting employees who are having issues in Staff Kiosk. 

When the Ghost Logon has been used to access Staff Kiosk as an employee, the username of the TASS.web user will be recorded in the Audits Log Grid with the text GHOST. 

*Date of Birth

Mandatory.

This field cannot be edited when this employee's record is involved in a pay run which is in progress. 

School Email

Use this field to record the Employee's internal school email address.

This email address will be used when emails are generated using various TASS programs.

Changes to this field will also appear on the Teacher record when the Employee and Teacher records are linked.

Signature

Use this field to add an employee's signature.

Signatures added here can be used when generating Academic Reports.

If the Employee is linked to a Teacher Record. This field also updates the ‘Signature’ field in TASS.web Student Admin > Teacher Records > Teacher Information > Teachers on the ‘General’ tab.

Indigenous Status

Use this field to record the employee's 'Indigenous Status' (a requirement for Census (Aus)).

Options include:

• Aboriginal.

• Torres Strait Islander.

• Aboriginal & Torres Strait Islander.

• Neither.

• Unknown.

For more information, refer to:

• The Census (Aus) TASS Knowledge Base article

• The SchoolsHub Non-Government Schools Census documentation.

Main Activity

Use this field to record the employee's 'Main Activity' (a requirement for Census (Aus)), i.e. The particular task that an employee performs during the day.

Options include:

• Administrative and clerical.

• Building Operations.

• Executive.

• Principal.

• Specialist Support.

• Teacher.

For more information, refer to:

• The Census (Aus) TASS Knowledge Base article

• The SchoolsHub Non-Government Schools Census documentation.

If staff are ineligible to be included in these categories, leave this field blank.

Position Title

A 100 character (maximum) field to enter the employee's full position title, e.g. Acting Deputy Principal - Administration.

The position title entered here can be printed on PD Certificates.

Click the ‘History’ link to view the selected Employee's previous 'Position Title/s'.

Click ‘Print All’ to produce the ‘Position Title History’ report in PDF format.

Supervisor

Supervisor information is used by the following Staff Kiosk programs to determine each employee's supervisor:

• Payroll/HR > PD Activities - My Staff (Maintain).

• Payroll/HR > My Staff Leave/Other Applications.

Enter or lookup the employee who is the supervisor of this employee.

A ‘yellow alert’ icon will display where the supervisor is no longer a current employee.

Click here for more information about the Supervisor Hierarchy.

Supervisor Hierarchy

The Supervisor Hierarchy is an organizational chart that lists every employee's immediate supervisor(s) and their position within the hierarchy.

The report uses the 'Supervisor' and 'Supervisor 2' fields on each employee's record to determine their position in the hierarchy.

• If an employee has no Supervisor entered, they will appear in the Level 1 column.

• Two employees cannot report to each other. This creates an infinite loop, and an error report will be produced when viewing the Supervisor Hierarchy.

• If an employee has both 'Supervisor' and 'Supervisor 2' fields populated, their name will appear twice on the report. 

The below Organisational chart (not produced from TASS) reflects the above Supervisor Hierarchy Report from TASS. 

The Supervisor Hierarchy report can be provided to administrators who are responsible for managing Online Leave Applications and PD Activities in Staff Kiosk, as the approval flows for these programs reference the Supervisor Hierarchy.

Online Leave Applications

When an employee submits an online Leave Application, the approval workflow begins, requiring each approver, in order, to approve the leave.

Each Leave / Other Type can be set up to include any or all of three approver work flows:
  1st)  the number of approvers, including the employee's immediate Supervisor(s), and any number of people up the employee's hierarchical structure.
  2nd)  the employee's Supervisor at a certain level, allowing lower level supervisors to be skipped.
  3rd)  a final designated approver, separate to the Supervisor Hierarchy.

Example approval workflow:

For 'Sick Leave', each employee must have:

       1st)  2 Supervisor approvals
      2nd)  Level 2 approval
       3rd)  Olive Brown is the designated final approver for all Sick Leave applications.

Gavin Rogers applies for sick leave.

• His immediate Supervisor, Lou Warry, the first of 2 supervisor approvers, receives the application by email and he approves.

• David Johnstone, the second of 2 supervisor approvers, then receives the application by email and he approves.

• Peter Baskins, as the Level 2 approver, then receives the application by email and he approves.

• Olive Brown, as the designated approver, receives the application by email and she approves.
  Gavin Rogers receives an email as each approval occurs.

PD Activities

When an employee adds a PD Activity that requires approval, their immediate supervisor can approve it.

Example approval workflow:

Gavin Rogers adds a PD activity in Staff Kiosk.

• His immediate Supervisor, Lou Warry, logs into Staff Kiosk and changes the status of the activity to Approved.

If an employee has both 'Supervisor' and 'Supervisor 2' fields populated, either can approve the leave application or PD Activity.

Supervisor 2

Where there is a second supervisor, enter or lookup the employee who is the second supervisor of this employee.

A ‘yellow alert’ icon will display where the supervisor is no longer a current employee.

Click here for more information about the Supervisor Hierarchy.

Supervisor Hierarchy

The Supervisor Hierarchy is an organizational chart that lists every employee's immediate supervisor(s) and their position within the hierarchy.

The report uses the 'Supervisor' and 'Supervisor 2' fields on each employee's record to determine their position in the hierarchy.

• If an employee has no Supervisor entered, they will appear in the Level 1 column.

• Two employees cannot report to each other. This creates an infinite loop, and an error report will be produced when viewing the Supervisor Hierarchy.

• If an employee has both 'Supervisor' and 'Supervisor 2' fields populated, their name will appear twice on the report. 

The below Organisational chart (not produced from TASS) reflects the above Supervisor Hierarchy Report from TASS. 

The Supervisor Hierarchy report can be provided to administrators who are responsible for managing Online Leave Applications and PD Activities in Staff Kiosk, as the approval flows for these programs reference the Supervisor Hierarchy.

Online Leave Applications

When an employee submits an online Leave Application, the approval workflow begins, requiring each approver, in order, to approve the leave.

Each Leave / Other Type can be set up to include any or all of three approver work flows:
  1st)  the number of approvers, including the employee's immediate Supervisor(s), and any number of people up the employee's hierarchical structure.
  2nd)  the employee's Supervisor at a certain level, allowing lower level supervisors to be skipped.
  3rd)  a final designated approver, separate to the Supervisor Hierarchy.

Example approval workflow:

For 'Sick Leave', each employee must have:

       1st)  2 Supervisor approvals
      2nd)  Level 2 approval
       3rd)  Olive Brown is the designated final approver for all Sick Leave applications.

Gavin Rogers applies for sick leave.

• His immediate Supervisor, Lou Warry, the first of 2 supervisor approvers, receives the application by email and he approves.

• David Johnstone, the second of 2 supervisor approvers, then receives the application by email and he approves.

• Peter Baskins, as the Level 2 approver, then receives the application by email and he approves.

• Olive Brown, as the designated approver, receives the application by email and she approves.
  Gavin Rogers receives an email as each approval occurs.

PD Activities

When an employee adds a PD Activity that requires approval, their immediate supervisor can approve it.

Example approval workflow:

Gavin Rogers adds a PD activity in Staff Kiosk.

• His immediate Supervisor, Lou Warry, logs into Staff Kiosk and changes the status of the activity to Approved.

If an employee has both 'Supervisor' and 'Supervisor 2' fields populated, either can approve the leave application or PD Activity.

Last Update By /

Last Update On

The TASS.web user to last edit this employee will be displayed along with the date and time the record was edited.

Click the 'View' link to display the changes.