How to Set Up Multiple Departments in Freshservice?
Quick Summary
Setting up multiple departments in Freshservice lets you route tickets accurately, control data visibility, tailor service catalogs for different teams, and generate department-level reports that reflect how each part of your organization actually uses IT support. This article walks through every step — from creating departments and assigning users to connecting departments with groups, SLA policies, and automation rules.
Freshservice is a cloud-based IT Service Management (ITSM) platform by Freshworks that unifies incident management, service requests, asset tracking, change control, and an employee self-service portal in one place. For a full overview of what the platform offers, visit Freshservice ITSM Software.
Most organizations that adopt Freshservice start with a single IT team managing support for the whole company. Over time, however, that single-team setup creates friction: HR submits requests alongside Engineering, Finance tickets mix with Facilities requests, and reports become impossible to interpret because everything lands in one undifferentiated queue.
The solution is to configure departments inside Freshservice — a structural layer that mirrors how your organization actually divides its people and services. Departments unlock targeted ticket routing, department-specific service catalogs, restricted data visibility, and granular reporting. This article reveals exactly how to plan, create, and manage multiple departments in Freshservice so your helpdesk scales cleanly alongside your organization.
What Are Departments in Freshservice and How Do They Differ from Groups?
Departments and groups are two distinct organizational structures in Freshservice that serve different purposes, and understanding the difference before you start building is essential. Confusing the two leads to a messy configuration that becomes harder to untangle as your instance grows.
Departments represent your organizational structure — the business divisions that appear on an org chart. They classify the people who submit tickets: IT, HR, Finance, Engineering, Legal, and so on. Groups, on the other hand, represent your support team structure — the clusters of agents who resolve tickets. A “Network Team” group handles networking issues; a “Desktop Support” group handles hardware.
How Do Departments and Groups Work Together in Freshservice?
| Concept | Represents | Who Belongs to It | Primary Use |
| Department | A business division (HR, Finance, Engineering) | Requesters — employees who submit tickets | Classify tickets by originating business unit; control portal visibility |
| Group | A support team (Network Team, Desktop Support) | Agents — IT staff who resolve tickets | Route tickets to the right resolver team; manage agent workload |
| Both | Used together in automation and reporting | Agents can also belong to departments as employees | Combine for rules like: IF Department = HR THEN assign to HR Support Group |
Consequently, when you build automation rules in Freshservice, departments and groups work as a pair: the department tells Freshservice where a ticket came from, and the group tells it where the ticket should go. Together, they form the backbone of intelligent ticket routing.
How Do You Plan a Department Structure Before Building It in Freshservice?
The most common mistake teams make when setting up departments is jumping straight into Freshservice without a plan. The result is a list of departments that partially overlaps with groups, misses some teams, and does not match the org chart — requiring a painful restructure six months later.
Before you create a single department in Freshservice, spend time mapping your organizational structure on paper or in a spreadsheet. Answer these three questions for each department you plan to create:
- Who submits tickets from this department? Identify the business unit, how many employees it contains, and who the department head is.
- Which support group resolves this department’s tickets? Map each department to the agent group that handles its requests so you can build routing rules later.
- Does this department need a separate service catalog or portal experience? Some departments — like HR or Facilities — benefit from a dedicated set of service items that other departments should not see.
What Does a Well-Planned Department Map Look Like?
| Department Name | Typical Employees | Resolver Group | Needs Custom Catalog? |
| Information Technology | IT staff, sysadmins, developers | IT Internal Support | No — uses full catalog |
| Human Resources | HR managers, recruiters, coordinators | HR IT Support Group | Yes — onboarding, offboarding items |
| Finance & Accounting | Accountants, analysts, controllers | Desktop Support Group | No — standard catalog |
| Engineering | Software engineers, QA, DevOps | Developer Support Group | Yes — dev tools, access requests |
| Facilities | Office managers, maintenance staff | Facilities IT Group | Yes — building systems, access cards |
| Legal & Compliance | Lawyers, paralegals, compliance officers | Security & Compliance Group | Yes — secure document tools |
| Sales & Marketing | Account executives, marketing managers | Desktop Support Group | No — standard catalog |
Additionally, this planning exercise often surfaces redundancies — for example, discovering that three departments all route to the same support group, which means you can simplify your automation rules considerably. Furthermore, it reveals which departments genuinely need customized portal experiences and which ones are perfectly served by the standard service catalog.
How Do You Create a New Department in Freshservice?
Creating departments in Freshservice is straightforward once your plan is in place. The entire process happens inside the Admin panel, and each department takes only a couple of minutes to configure.
- Log in to Freshservice as an Administrator.
- Click the Admin icon (gear symbol) in the left navigation sidebar.
- Under the User Management section, select Departments.
- Click the New Department button in the top-right corner.
- Fill in the department details (see configuration fields below).
- Click Save to create the department.
What Information Do You Enter When Creating a Department?
| Field | What to Enter | Tips |
| Department Name | The official name of the business unit | Match your org chart exactly to avoid confusion — use “Human Resources” not “HR team” |
| Description | A short explanation of what this department does | Useful for administrators; appears in the department list for reference |
| Head of Department | The manager or director who leads this unit | Freshservice can notify the head when department-level reports are generated |
| Prime User | A designated point of contact in the department | Often the same as the head, but can be an EA or coordinator instead |
| Domains | Email domains associated with this department | Freshservice auto-assigns users to departments based on their email domain |
The Domains field deserves particular attention. When you enter an email domain (for example, hr@yourcompany.com using the yourcompany.com domain combined with a department prefix rule), Freshservice can automatically classify incoming tickets by department without agents having to manually tag each one. This automation becomes increasingly valuable as ticket volume grows.
How Do You Add Users and Agents to Departments in Freshservice?
After creating your departments, the next step is populating them with the right people. Freshservice handles department membership for two distinct user types — requesters (employees who submit tickets) and agents (IT staff who resolve tickets) — through slightly different paths.
How Do You Assign Requesters to a Department?
Requesters — the employees across your organization who use Freshservice to submit tickets — get assigned to departments through their user profile. Freshservice offers three ways to manage this assignment at scale:
- Manual assignment — Go to Admin > Requesters, open any individual user’s profile, and select their department from the Department dropdown. This works well for small teams or occasional reassignments.
- Bulk import via CSV — Navigate to Admin > Requesters > Import and upload a CSV file that includes a Department column. Freshservice reads the department name from each row and assigns users accordingly. This is the fastest method for initial setup when you are onboarding hundreds of users at once.
- Directory sync (LDAP / Active Directory / Azure AD) — Freshservice integrates with enterprise directories and can map Active Directory Organizational Units (OUs) or Azure AD groups directly to Freshservice departments. This approach keeps department membership in sync automatically as employees join, move teams, or leave the organization.
How Do You Associate Agents with Departments in Freshservice?
Agents belong to groups rather than departments in their primary support role, but they also carry a department attribute in their profile that records which business unit they personally belong to. Set this in Admin > Agents by opening an agent’s profile and selecting their department. This distinction matters for reporting: it lets you analyze how many IT resources each department consumes and build accurate cost-allocation reports for IT budget conversations.
How Do You Use Departments to Control Ticket Routing in Freshservice?
One of the most powerful uses of departments in Freshservice is automating ticket routing so that every ticket lands in the right agent group without manual intervention. Freshservice’s Workflow Automator lets you build rules that read the submitting user’s department and act accordingly.
What Does a Department-Based Routing Rule Look Like?
Here is a practical example of how to build a department-based routing automation in Freshservice. Navigate to Admin > Workflow Automator, create a new workflow triggered by Ticket Created, and add conditions and actions as follows:
| Workflow Component | Configuration Example |
| Trigger | Ticket is Created |
| Condition 1 | Requester’s Department is Human Resources |
| Condition 2 | Ticket Type is Service Request |
| Action 1 | Assign to Group: HR IT Support Group |
| Action 2 | Set Priority: Medium |
| Action 3 | Send Email Notification to: HR Support Group |
Furthermore, you can chain multiple department conditions in a single workflow or create separate workflows for each department depending on how different the routing logic needs to be. For teams with straightforward routing — where every department maps to one support group — a single multi-condition workflow handles all routing neatly. For complex environments where departments have sub-routing rules based on ticket type or urgency, separate per-department workflows give you cleaner logic that is easier to maintain.
How Do You Restrict Service Catalog Visibility by Department in Freshservice?
Not every service item in your catalog applies to every department. Showing HR staff a “Request Developer Sandbox” option, or showing engineers a “Request Payroll System Access” form, adds clutter and confusion to the self-service portal. Freshservice solves this through per-service-item visibility controls that restrict which departments see which catalog entries.
To configure catalog visibility by department, go to Admin > Service Catalog, open any service item, and scroll to the Visibility section. There you choose between All Users, Specific Departments, Specific Requesters, or Agents Only. Select Specific Departments and then check the departments that should see this item. From that point forward, Freshservice filters the portal display dynamically based on the logged-in user’s department — each employee sees only the services relevant to their role.
What Are the Most Common Department-Specific Catalog Configurations?
| Service Item | Visible To | Hidden From |
| New Employee Laptop | IT, HR, Department Heads | All other departments |
| Payroll System Access Request | Finance & Accounting, HR | Engineering, Sales, Facilities |
| Developer Sandbox Environment | Engineering | HR, Finance, Legal, Facilities |
| Legal Document Signing Tool | Legal & Compliance, HR, Finance | Engineering, Sales, IT internal |
| Office Access Card Request | Facilities, HR | All other departments |
| CRM Account Setup | Sales & Marketing | All other departments |
How Do You Generate Department-Level Reports in Freshservice?
Once your departments are set up and tickets flow through them, Freshservice Analytics unlocks reporting dimensions that were impossible with a single undifferentiated queue. Department-level reporting answers the questions IT leaders care most about — which departments generate the most tickets, which take the longest to resolve, and where self-service adoption is strongest.
- Ticket Volume by Department — Shows how many tickets each department submits per month. This report highlights which business units put the greatest demand on IT resources and often feeds into cost-allocation conversations.
- Average Resolution Time by Department — Reveals whether some departments consistently experience slower resolution than others, which may indicate routing problems, under-staffed support groups, or unusually complex ticket types.
- SLA Compliance by Department — Measures whether the team meets SLA targets for each department. A department with consistently low SLA compliance often signals a mismatch between the SLA policy applied and the actual complexity of that department’s tickets.
- Self-Service Rate by Department — Tracks how frequently employees from each department use the portal versus email or phone. Departments with low self-service rates are strong candidates for targeted portal improvement or knowledge base expansion.
Additionally, Freshservice lets you schedule these reports as automated email digests to department heads and IT managers. This keeps stakeholders informed without requiring them to log in to Freshservice themselves, and it builds the habit of data-driven IT conversations across the organization.
What Are the Best Practices for Managing Multiple Departments in Freshservice?
A clean department structure pays dividends every day in routing accuracy, reporting quality, and administrative simplicity. Here are the practices that experienced Freshservice administrators follow to keep their department configurations healthy over time:
- Mirror your org chart precisely — Use the same department names your HR system and org chart use. Inconsistencies between Freshservice and HR data create confusion during audits and make directory sync unreliable.
- Sync with your directory service where possible — Manual department membership management does not scale beyond a few hundred users. LDAP, Active Directory, or Azure AD integration keeps membership accurate automatically.
- Review department structure after reorgs — When your company restructures, update Freshservice departments immediately. Stale department data corrupts routing rules and reports.
- Avoid creating departments for every sub-team — Departments should reflect major business divisions, not every team and sub-team. Over-granular departments make automation rules exponentially more complex.
- Assign a department head to every department — The Head of Department field in Freshservice enables escalation rules and report distribution. Leaving it blank disables these features silently.
- Test routing rules when you add a new department — After creating a department and its automation rules, submit a test ticket as a user from that department and verify it routes to the correct group with the correct priority.
What Should You Take Away About Setting Up Multiple Departments in Freshservice?
Setting up multiple departments in Freshservice is one of the most impactful structural decisions you make when maturing your ITSM setup beyond a basic single-queue help desk. Departments give Freshservice the organizational context it needs to route tickets intelligently, surface the right catalog items to the right employees, restrict data to the right audiences, and generate reports that actually reflect how different parts of your business consume IT services.
Moreover, the investment in planning your department structure upfront — mapping each department to its resolver group, identifying which catalog items it needs, and designing the right automation rules — pays back many times over in reduced manual triage, cleaner reporting, and a self-service portal that employees from every team find genuinely useful. Freshservice provides the tools to build this structure without developer skills; the Admin panel walks administrators through every configuration step with an intuitive interface.
As your organization grows, keep your Freshservice department structure synchronized with your HR system, review it after every reorganization, and use department-level analytics to continuously improve routing accuracy and service quality. The result is an ITSM platform that scales cleanly alongside your business — not one that fights against your org chart. Explore the full capabilities of the platform at Freshservice ITSM Software.
Frequently Asked Questions
In Freshservice’s standard configuration, each requester belongs to a single department. This one-to-one relationship reflects how most organizations structure their employee records — a person works in one business unit at a time. However, matrix organizations or employees with cross-functional roles sometimes need a more flexible setup. In those cases, the most practical solution is to assign the user to their primary department in Freshservice and handle secondary associations through agent groups or ticket tags rather than department membership. If you use a directory sync, the department value typically comes directly from the employee’s HR record, which already handles the primary-department designation.
Departments do not attach directly to SLA policies in Freshservice the way business hours or ticket categories do. However, departments influence SLA policy application indirectly through automation rules. You can build a Workflow Automator rule that detects a ticket’s department and then applies a specific SLA policy using the Change SLA Policy action. For example, tickets from the Executive department can trigger a premium SLA policy with tighter response targets, while standard department tickets follow the default SLA. This indirect connection gives you the flexibility to differentiate SLA treatment by department without needing a direct department-to-SLA mapping in the platform’s settings.
