Definitions

Before you start, it's a good idea to understand what is meant by each of the terms defined in JPAC.

People: Individual staff or team members in your organisation (e.g. employees, contractors, volunteers) for whom you manage compliance and keep records for. They may or may not also be "users".

User: Anyone in your organisation who has permission to log into JPAC. There are two types of users - standard users and administrators. 

1. Standard user: is a member of your organisation who can log into JPAC, to view and change information according to the permissions that have been applied to them by the administrator.
2. Administrator: is able to set up, manage and administer JPAC with no limitations/restrictions, and has the ability to control access given to standard users. Every organisation needs to have at least one administrator.

Requirements: Can also be defined as "competencies", and may include training, qualifications, experience, statutory checks, licenses, or anything that you require people in your organisation to be able to demonstrate or achieve.

Assignments:  Link Requirements to People.

Records: Document the Requirements a Person has attained.

Compliance:  The score calculated from comparing the Assignments to the Records.

Classifications of People: Can be done via the following methods -

1. Org units: Define the structure of your organisation from a people perspective such as departments and/or geographic locations. Every Person must exist in at least one Org Unit.
2. Roles: Every Person has to have at least one Role assigned to them such as office administrator, support worker, accountant.
3. Employment types: i.e. full time, part time, volunteer, contractor, consultant.
4. Tags: An alternate way of labelling a group of people that isn't based on Org Units, Roles, or Employment Types. For example, fire training for people who work on the 5th floor.

Classifications of requirements: There are several ways of doing this -

1. Categories: Putting things under headings like induction, professional development.
2. Requirement types: Things like licenses, training, qualifications or statutory checks.
3. Tags: An alternate way of labelling a Requirement that isn't based on categories or requirement types. For example, you can group a set of Requirements by the tag '10+ years experience' if these are the Requirements that would be expected from employees that have been in their Role for more than 10 years.

Employees cannot look at data for another employee, or any other broad statistics about the company.