Department

Department is a tree-structured master that places employees in teams within a Company. Departments drive leave approvers, expense approvers, recruitment analytics, and performance cycle filters.

Help URL: https://smoothhiring.com/help/hrms/people/department

Table of contents

1. Overview
2. Who uses Department
3. Desk paths
4. Building the department tree
5. Department and approvals
6. HR Settings interaction
7. Workflow examples
8. Common mistakes
9. Troubleshooting

Overview

Each Department belongs to one Company and may have a Parent Department. Employees reference a leaf or mid-level department. The org chart uses Reports to on Employee, not the department tree alone — but department still matters for policies.

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 Department

HR operations maintains the tree; managers consume it via reports and team leave views.

Desk paths

Building the department tree

1. Create root department per company (e.g. "All Departments" or company name).
2. Add child departments: Engineering, Sales, HR, Operations.
3. Add sub-teams as nested children.
4. Assign each Employee to the most specific department they belong to.

Avoid duplicate names under the same parent; use clear naming like Engineering - Backend.

Department and approvals

Leave Approver and Expense Approver on Employee often match the department head. When moving employees between departments, update approver fields if your policy requires department-head approval.

HR Settings interaction

Show leaves of all department members in calendar (HR Settings) controls whether employees see colleagues' leave on the calendar — privacy vs transparency tradeoff.

Workflow examples

flowchart TD
  Root[Company Root Dept] --> Eng[Engineering]
  Root --> Sales[Sales]
  Eng --> BE[Backend]
  Eng --> FE[Frontend]

Reorg workflow: create new department → move employees → deactivate old department if empty.

Common mistakes

Troubleshooting

Department analytics

Recruitment Analytics and headcount dashboards filter by department. Keep department codes stable year-over-year for trending.

When acquiring a company, map legacy department codes to Smooth HR tree before bulk employee import.

Frequently asked questions

Branch vs Department?

Branch is location; Department is org unit. Employee can have both.

Can one employee be in two departments?

Single department field — use primary department; projects may track matrix elsewhere.

Related guides

• People overview
• Company
• Designation
• Employee records

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.