Designation
Designation defines job titles (Software Engineer, HR Manager, Warehouse Associate) used across Employee, Job Opening, Job Offer, Staffing Plan, and onboarding template matching.
Help URL: https://smoothhiring.com/help/hrms/people/designation
Table of contents
- Overview
- Who uses Designation
- Desk paths
- Creating designations
- Designation in recruitment
- Staffing plans and vacancies
- Common mistakes
- Troubleshooting
Overview
Designations are company-agnostic titles in standard HRMS — employees pick a designation from the list. They align with Job Opening titles and Salary Structure assignments for payroll bands.
| Linked process | Role of designation |
|---|---|
| Job Opening | Required on published role |
| Job Offer | Copied to Employee on hire |
| Staffing Plan | Vacancy counts per designation |
| Appraisal | Template matching by designation |
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}.
Who uses Designation
| 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 |
Recruiters and HR create designations before opening roles. Payroll may map salary structures by designation or grade.
Desk paths
| Action | Path |
|---|---|
| Designation list | /app/designation |
| People → Setup | /desk/people |
Creating designations
- People → Setup → Designation → Add Designation.
- Enter Designation Name (e.g. Senior Accountant).
- Optional description for internal use.
- Save. Use consistently in Job Openings — avoid near-duplicate titles (Sr Accountant vs Senior Accountant).
Designation in recruitment
Job Opening requires designation. Job Applicant inherits job title from opening. Interview and Job Offer reference the same designation. When Create Employee runs from Job Offer, designation maps to Employee.
If designation on offer does not exist on Employee form dropdown, create the master first.
Staffing plans and vacancies
Staffing Plan lines count vacancies by designation and date range. HR Settings → Check Vacancies blocks Job Offer when plan is exhausted. See Job Opening.
Common mistakes
| Mistake | Fix |
|---|---|
| Typos in designation names | Standardize list; merge duplicates carefully |
| Offer designation not in master | Create before offer |
| Mixing designation and grade | Use Employee Grade for bands; designation for title |
Troubleshooting
| Issue | Fix |
|---|---|
| Vacancy error on Job Offer | Staffing plan or disable check in HR Settings |
| Designation missing on import | Pre-create all titles in CSV |
Title governance
Publish an internal title catalog before go-live. HR, recruitment, and payroll should share one list to prevent offer letter titles that differ from payroll records.
For international hires, you may use global designations with local job codes in a custom field if your policy requires it.
Frequently asked questions
Is designation required on Employee?
Yes in most configurations — required for recruitment and reporting.
Can designation change on promotion?
Use Employee Promotion in Performance or edit Employee with effective date note.
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.