LiveSchools365 Role Training Kit — HR

Trainer-grade · 2026-09-23 · ~23 min · https://liveschools365.com

USER TRAINING (not QA smoke).

1. Purpose

Run people operations: leave desk and payroll setup through runs.

Business scenario

HR/payroll week: you review leave, open payroll, and confirm the HR Implementation Guide steps for your role.

Learning outcomes

• Complete the HR Implementation Guide track end-to-end (~23 minutes).
• Run people operations: leave desk and payroll setup through runs.
• Use official menu paths instead of informal messaging for auditable school work.
• Know when to Mark done and how to resume from /implement or Trial Journey.

2. Sign in

• Login: /school-management-software-login
• User: hr@liveschool
• Password: LiveSchool@123
• Guide: /implement/hr

3–4. Guided workflows

4.1 Open leave management

Main task: Reach the HR leave desk

Why: Leave policy, student leave, and staff leave sit under H.R / Leave.

Menu: H.R / Leave → Leave Management
Route: /leave-management

How to:

1. Open Leave Management.
2. Note any pending student or staff requests.
3. Mark done.

Fields:

• Report parameters — Define the authorized leave population and reporting period.
• Export to Excel — Download the generated result with metadata and parameters.
• Report parameters — Define the exam population and analysis scope.
• Export to Excel — Download the generated result with branding, metadata, parameters, and rows.
• Grade — Name the band, such as A+ or F.

Practice:

• Open live form: /leave-management
• Follow menu path: H.R / Leave → Leave Management
• Practice: one-day Casual leave with reason 'Family appointment'

Expected: After this step, “Reach the HR leave desk” is true on the live system, and the Implementation Guide step “Open leave management” can be Mark done.

Mistakes:

• If this step is skipped: Leave policy, student leave, and staff leave sit under H.R / Leave.
• Approving without reading dates/reason → payroll and coverage conflicts.

4.2 Review a staff leave request

Main task: Approve or inspect staff leave

Why: HR reviews staff leave before balances update.

Menu: H.R / Leave → Staff Leave → Approvals
Route: /staff-leave/approvals

How to:

1. Open Staff Leave → Approvals.
2. Open a pending request if any.
3. Approve with a short remark, or Skip if the queue is empty.
4. Mark done.

Practice:

• Open live form: /staff-leave/approvals
• Follow menu path: H.R / Leave → Staff Leave → Approvals
• Practice: one-day Casual leave with reason 'Family appointment'

Expected: After this step, “Approve or inspect staff leave” is true on the live system, and the Implementation Guide step “Review a staff leave request” can be Mark done.

Mistakes:

• If this step is skipped: HR reviews staff leave before balances update.
• Approving without reading dates/reason → payroll and coverage conflicts.

4.3 Open payroll

Main task: Reach salary processing

Why: Payroll needs staff records and components before a run.

Menu: Finance → Payroll
Route: /finance/payroll

How to:

1. Open Finance → Payroll.
2. Note whether setup looks ready.
3. Mark done.

Practice:

• Open live form: /finance/payroll
• Follow menu path: Finance → Payroll
• Practice: open payroll workspace and note current pay period label

Expected: After this step, “Reach salary processing” is true on the live system, and the Implementation Guide step “Open payroll” can be Mark done.

Mistakes:

• If this step is skipped: Payroll needs staff records and components before a run.
• Using WhatsApp instead of the official form — the audit trail will be missing.

4.4 Review payroll setup

Main task: Confirm salary components exist

Why: Components must exist before you calculate a run.

Menu: Finance → Payroll → Setup
Route: /finance/payroll/setup

How to:

1. Open Payroll setup.
2. Review earnings/deduction components.
3. Add a basic salary component if none exist.
4. Mark done.

Practice:

• Open live form: /finance/payroll/setup
• Follow menu path: Finance → Payroll → Setup
• Practice: open payroll workspace and note current pay period label

Expected: After this step, “Confirm salary components exist” is true on the live system, and the Implementation Guide step “Review payroll setup” can be Mark done.

Mistakes:

• If this step is skipped: Components must exist before you calculate a run.
• Using WhatsApp instead of the official form — the audit trail will be missing.

4.5 Process a sample payroll run

Main task: Calculate pay for a small staff set

Why: A run is the practical HR/finance handoff for salaries.

Menu: Finance → Payroll → Runs
Route: /finance/payroll/runs

How to:

1. Open Payroll runs.
2. Select a short trial period.
3. Calculate for available staff.
4. Review totals; posting is optional on trial.
5. Mark done.

Practice:

• Open live form: /finance/payroll/runs
• Follow menu path: Finance → Payroll → Runs
• Practice: open payroll workspace and note current pay period label

Expected: After this step, “Calculate pay for a small staff set” is true on the live system, and the Implementation Guide step “Process a sample payroll run” can be Mark done.

Mistakes:

• If this step is skipped: A run is the practical HR/finance handoff for salaries.
• Using WhatsApp instead of the official form — the audit trail will be missing.

5. Capstone checklist

• □ Open leave management
• □ Review a staff leave request
• □ Open payroll
• □ Review payroll setup
• □ Process a sample payroll run

6. Knowledge check

Q: What is the first main task on the HR track?
A: Reach the HR leave desk

Q: Which menu path opens “Open leave management”?
A: H.R / Leave → Leave Management

Q: Why does “Review a staff leave request” matter?
A: HR reviews staff leave before balances update.

Q: What happens if you finish a live form but do not Mark done?
A: Later Implementation Guide steps stay locked / progress is incomplete.

Q: Demo username for this kit?
A: hr@liveschool

7. Video