Training
Training Program and Training Event schedule learning for employees in Smooth HR Tenure module. Programs define curricula; events are scheduled sessions with attendees, feedback (Training Feedback), and results (Training Result).
Help URL: https://smoothhiring.com/help/hrms/tenure/training
Table of contents
- Overview
- Desk paths
- Training Program
- Training Event workflow
- Feedback and results
- Who uses training
- Common mistakes
- Troubleshooting
Overview
| DocType | Role |
|---|---|
| Training Program | Catalog entry (Safety, Leadership) |
| Training Event | Dated session with roster |
| Training Feedback | Post-session survey |
| Training Result | Pass/fail or scores |
Smooth HR runs on Frappe v16. Module sidebars (People, Recruitment, Expenses, Performance, Tenure, NextAI) appear after login. DocType lists use /app/{slug}; workspace homes use /desk/{module}.
Desk paths
| Action | Path |
|---|---|
| Training Program | /app/training-program |
| Training Event | /app/training-event |
| Training Feedback | /app/training-feedback |
| Training Result | /app/training-result |
| Tenure workspace | /desk/tenure |
Training Program
- Tenure → Setup → Training Program → Add.
- Name, description, default trainer, duration.
- Reuse program across recurring events.
Training Event workflow
flowchart TD
Prog[Training Program] --> Ev[Training Event]
Ev --> Emp[Add employees]
Ev --> Run[Conduct session]
Run --> FB[Training Feedback]
Run --> Res[Training Result]
- Create Training Event; link program.
- Set schedule, location, trainer.
- Add employees to roster.
- After event, collect feedback and record results.
Feedback and results
Training Feedback captures participant ratings. Training Result stores completion status for compliance (e.g. mandatory safety training).
Who uses training
| Role | Typical use |
|---|---|
| HR Manager | Full create/submit/cancel; setup masters; reports |
| HR User | Day-to-day transactions; may need approval rules |
| Employee | Self-service where enabled |
| System Manager | Site-wide configuration, integrations, NextAI keys |
HR schedules; employees attend; managers track team completion.
Common mistakes
| Mistake | Fix |
|---|---|
| Event without employees | Add roster before session |
| No program link | Select program for reporting |
| Missing results | Record for audit trails |
Troubleshooting
| Issue | Fix |
|---|---|
| Employee not notified | Email on Employee; notify action |
| Duplicate events | Copy event for new date |
| Report incomplete | Submit Training Result |
Compliance training
Run quarterly reports on mandatory programs. Link events to departments for role-based assignments.
Frequently asked questions
External trainers?
Set trainer name on event; no Employee link required.
Skills map?
Employee Skill Map in Tenure setup complements training history.
Related guides
Additional operational detail
Smooth HR v16 organizes HR into module workspaces accessible from the desktop app switcher. Each module sidebar mirrors production fixtures in the HRMS app: People at /desk/people, Recruitment at /desk/recruitment, Expenses at /desk/expenses, Performance at /desk/performance, Tenure at /desk/tenure, and NextAI at /desk/nextai. DocType routes follow /app/{slug} where slug is the lowercased DocType with spaces replaced by hyphens.
HR Managers configure masters and approvals; HR Users run daily transactions; Employees interact through self-service when User records link to Employee and roles permit; System Managers own site configuration including NextAI API credentials. Before go-live, validate Role Permissions Manager entries for each DocType mentioned in this guide.
When migrating from spreadsheets, import Company and Department before Employee, then recruitment and expense histories. Use Data Import templates and fix validation errors row-by-row rather than bulk-deleting partial loads. Clear desk cache after fixture updates so sidebars reflect the latest Smooth HR layout.
For payroll-adjacent HR data, keep Employee company and department aligned with cost centers. For recruitment, remember Job Applicant documents use email as the primary key. For expenses, settle Employee Advance balances on Expense Claim submission. For performance, run Appraisal Cycle to batch-create Appraisal records. For tenure, complete Employee Separation projects before deactivating employees. For NextAI, store Gemini or OpenAI keys only in NextAI Settings and review usage logs before retention cleanup runs.
Additional operational detail
Smooth HR v16 organizes HR into module workspaces accessible from the desktop app switcher. Each module sidebar mirrors production fixtures in the HRMS app: People at /desk/people, Recruitment at /desk/recruitment, Expenses at /desk/expenses, Performance at /desk/performance, Tenure at /desk/tenure, and NextAI at /desk/nextai. DocType routes follow /app/{slug} where slug is the lowercased DocType with spaces replaced by hyphens.
HR Managers configure masters and approvals; HR Users run daily transactions; Employees interact through self-service when User records link to Employee and roles permit; System Managers own site configuration including NextAI API credentials. Before go-live, validate Role Permissions Manager entries for each DocType mentioned in this guide.
When migrating from spreadsheets, import Company and Department before Employee, then recruitment and expense histories. Use Data Import templates and fix validation errors row-by-row rather than bulk-deleting partial loads. Clear desk cache after fixture updates so sidebars reflect the latest Smooth HR layout.
For payroll-adjacent HR data, keep Employee company and department aligned with cost centers. For recruitment, remember Job Applicant documents use email as the primary key. For expenses, settle Employee Advance balances on Expense Claim submission. For performance, run Appraisal Cycle to batch-create Appraisal records. For tenure, complete Employee Separation projects before deactivating employees. For NextAI, store Gemini or OpenAI keys only in NextAI Settings and review usage logs before retention cleanup runs.
Last updated: May 2026
Additional operational detail
Smooth HR v16 organizes HR into module workspaces accessible from the desktop app switcher. Each module sidebar mirrors production fixtures in the HRMS app: People at /desk/people, Recruitment at /desk/recruitment, Expenses at /desk/expenses, Performance at /desk/performance, Tenure at /desk/tenure, and NextAI at /desk/nextai. DocType routes follow /app/{slug} where slug is the lowercased DocType with spaces replaced by hyphens.
HR Managers configure masters and approvals; HR Users run daily transactions; Employees interact through self-service when User records link to Employee and roles permit; System Managers own site configuration including NextAI API credentials. Before go-live, validate Role Permissions Manager entries for each DocType mentioned in this guide.
When migrating from spreadsheets, import Company and Department before Employee, then recruitment and expense histories. Use Data Import templates and fix validation errors row-by-row rather than bulk-deleting partial loads. Clear desk cache after fixture updates so sidebars reflect the latest Smooth HR layout.
For payroll-adjacent HR data, keep Employee company and department aligned with cost centers. For recruitment, remember Job Applicant documents use email as the primary key. For expenses, settle Employee Advance balances on Expense Claim submission. For performance, run Appraisal Cycle to batch-create Appraisal records. For tenure, complete Employee Separation projects before deactivating employees. For NextAI, store Gemini or OpenAI keys only in NextAI Settings and review usage logs before retention cleanup runs.
Additional operational detail
Smooth HR v16 organizes HR into module workspaces accessible from the desktop app switcher. Each module sidebar mirrors production fixtures in the HRMS app: People at /desk/people, Recruitment at /desk/recruitment, Expenses at /desk/expenses, Performance at /desk/performance, Tenure at /desk/tenure, and NextAI at /desk/nextai. DocType routes follow /app/{slug} where slug is the lowercased DocType with spaces replaced by hyphens.
HR Managers configure masters and approvals; HR Users run daily transactions; Employees interact through self-service when User records link to Employee and roles permit; System Managers own site configuration including NextAI API credentials. Before go-live, validate Role Permissions Manager entries for each DocType mentioned in this guide.
When migrating from spreadsheets, import Company and Department before Employee, then recruitment and expense histories. Use Data Import templates and fix validation errors row-by-row rather than bulk-deleting partial loads. Clear desk cache after fixture updates so sidebars reflect the latest Smooth HR layout.
For payroll-adjacent HR data, keep Employee company and department aligned with cost centers. For recruitment, remember Job Applicant documents use email as the primary key. For expenses, settle Employee Advance balances on Expense Claim submission. For performance, run Appraisal Cycle to batch-create Appraisal records. For tenure, complete Employee Separation projects before deactivating employees. For NextAI, store Gemini or OpenAI keys only in NextAI Settings and review usage logs before retention cleanup runs.
Smooth LMS (training)
| Guide | Link |
|---|---|
| LMS help home | smoothhiring.com/help/lms |
| HRMS + LMS overview | lms/hrms-integration/overview |
| Auto-provision LMS access | lms/hrms-integration/employee-auto-provisioning |
| Onboarding mandatory training | lms/hrms-integration/onboarding-mandatory-training |
| Compliance vs certificates | lms/hrms-integration/compliance-vs-lms-certificates |
| Mandatory courses | lms/courses/mandatory-training-and-validity |
| Course categories (folders) | lms/courses/categories-and-tags |