How to Build Approval Workflows in Freshservice

Approval bottlenecks slow down IT teams, frustrate employees, and introduce compliance risk. When every service request, change, or procurement decision waits in someone’s inbox for manual review, the entire service desk loses momentum. Freshservice solves this problem with a structured, highly configurable approval workflow engine that automates the routing, notification, escalation, and tracking of approvals across your entire organization.

Whether your team needs a simple one-step sign-off on a software request or a full multi-level hierarchy with Change Advisory Board (CAB) involvement, Freshservice gives you the tools to build it — without writing a single line of code. This guide walks you through everything you need to know to build, configure, and manage approval workflows in Freshservice effectively.

---

Quick Summary

• Freshservice supports automated approval workflows for service requests, changes, problems, and more — all built through a visual, no-code Workflow Automator.
• The approval framework uses approval groups, approval chains, and four configurable approval rules: Everyone, Anyone, Majority, and First Responder.
• Change management in Freshservice includes dedicated CAB (Change Advisory Board) support with scheduled meetings, structured agendas, and role-based voting.
• Freshservice introduced a new approval framework in 2025, replacing legacy approval behavior with non-blocking workflow execution and named approval groups.

---

What Is the Freshservice Approval Framework and How Does It Work?

Freshservice’s approval system consists of several interconnected components that work together to define who approves requests, under what rules, and in what sequence.

What Are Approvers, Approval Groups, and Approval Chains?

Understanding the structural components of Freshservice approvals is essential before you start building workflows.

Approvers are the individuals who receive approval requests. According to Freshservice’s official documentation, approvers can include “department heads, reporting managers, agent groups, or users as part of a Change Advisory Board (CAB).” You can also designate users of an impacted service as approvers.

Approval Groups are sets of approvers combined under a single approval rule. Within each group, the rule defines whether the group’s decision requires input from everyone, any single member, a majority, or just the first person to respond.

Approval Chains define the sequence in which groups receive approval requests. A chain can require all groups to approve sequentially — for instance, a manager first, then a department head, then the CAB — or allow parallel execution where multiple groups review simultaneously.

What Are the Four Approval Rules in Freshservice?

Freshservice lets you assign one of four rules to each approval group:

Approval Rule	How It Works	Best Use Case
Everyone	All members of the group must approve before the workflow proceeds	High-stakes changes requiring unanimous consensus (e.g., major infrastructure changes)
Anyone	The first member to approve triggers workflow continuation	Fast-track approvals where any authorized person’s sign-off is sufficient
Majority	More than half the group must approve	Committee-style decisions like CAB reviews on medium-risk changes
First Responder	The first person to cast a vote (approve or reject) determines the outcome	Emergency approvals where speed outweighs consensus

Choosing the right rule for each group and each scenario is one of the most impactful configuration decisions you make when building approval workflows in Freshservice.

---

How Do You Build a Service Request Approval Workflow in Freshservice?

Service request approvals are among the most common use cases for Freshservice approval workflows. Every time an employee requests software, hardware, access, or a specialized service, the right people need to authorize it — consistently, quickly, and with a full audit trail.

How Do You Access the Workflow Automator for Approval Configuration?

Navigate to Admin → Automation & Productivity → Workflow Automator. In multi-workspace accounts, global approval workflows appear under Admin → Global Settings → Automation & Productivity → Automation → Workflow Automator, while workspace-specific workflows live under each workspace’s admin settings.

Global workflows always execute first, followed by workspace-level workflows — so workspace rules can override global defaults when needed.

What Are the Steps to Build a Multi-Level Service Request Approval Workflow?

The following steps demonstrate how to build a hierarchical approval workflow — for example, one where a service request for a MacBook requires sign-off from both the requester’s reporting manager and the department head before fulfillment begins.

1. Go to Admin → Workflow Automator and click “New Automator.”
2. Select Ticket as the module.
3. Name the workflow clearly — for example, “MacBook Request — Manager + Department Head Approval.”
4. Set the trigger event to “Service Request is Raised.”
5. Drag a Condition block from the sidebar. Set the condition to: Requested Items includes Apple MacBook.
6. Drag an Action block and connect it to the condition’s “True” branch.
7. Inside the Action block, select “Request for Approval” from the action dropdown.
8. Add the first approval group: name it “Reporting Manager Approval” and select the reporting manager as the approver. Set the rule to Everyone (or Anyone if the manager role is shared across several people).
9. Add a second approval group inside the same action: name it “Department Head Approval” and add the department head. Set the rule as needed.
10. Define the “Execute workflow when” condition — for instance, “All approval groups are approved” — to ensure both sign-offs must occur before the workflow proceeds.
11. Connect the “Approved” branch to a fulfillment action, such as assigning the ticket to the IT Procurement group.
12. Connect the “Rejected” branch to a notification action, informing the requester of the rejection reason.
13. Click “Save and Activate.”

As Freshservice’s official documentation confirms, “when the reporting manager approves the service request, the workflow proceeds to process the next action” — in this case, routing to the department head’s approval group.

How Do You Configure Approval Reminders in Freshservice?

Approvals stall when approvers forget to respond. Freshservice lets you set automatic reminder emails that fire at configurable intervals — for instance, every 24 hours — until the approver takes action. Configure this through Admin → Email Notifications → Tickets → Service Request Approval and define the reminder frequency.

Additionally, approvers can respond directly from their email inbox. Freshservice sends them an email where they reply with a keyword to approve or reject — removing the need to log in to the platform for routine approvals.

---

How Do You Set Up Change Management Approval Workflows in Freshservice?

Change management approvals in Freshservice operate at a deeper level than service request approvals. They involve structured change lifecycles, categorized change types, and a dedicated CAB framework for collaborative review.

What Change Types Does Freshservice Support?

Freshservice defines four change types, each with its own default approval and lifecycle requirements:

Change Type	Description	CAB Required?
Standard Change	Pre-planned, pre-approved, low-risk, recurring changes (e.g., OS upgrades)	No
Minor Change	Low-impact changes that still proceed through the full lifecycle (e.g., website updates)	Yes
Major Change	Medium-to-high impact changes with potential financial implications (e.g., data center migration)	Yes, plus management approval
Emergency Change	Immediate fixes requiring fast authorization; formal review happens after implementation (e.g., security patches)	Emergency CAB approval

Each change type has its own lifecycle defined in Admin → Service Management → Service Desk Settings → Change Lifecycle. Admins can customize each lifecycle with specific statuses, mandatory transition fields, and approval gate requirements.

What Is the CAB and How Do You Configure It in Freshservice?

The Change Advisory Board (CAB) gives change managers a structured way to gather expert input before authorizing high-risk or high-impact changes. As Freshservice’s documentation explains, “the CAB provides an easy way to gather insights from multiple users who could contribute to the decision and record all their activities and discussions properly in your service desk.”

To set up a CAB in Freshservice:

1. Navigate to Admin → User Management → CAB (or Admin → Global Settings → User Management → CAB for multi-workspace accounts).
2. Click “New CAB” and provide a name and description.
3. Click “Add Members” to add approvers to the CAB one by one.
4. Save the CAB.

Freshservice supports multiple CABs for different domains — for instance, a Security CAB, an Infrastructure CAB, and a Vendor CAB. A single agent can belong to several CABs simultaneously and receives independent votes in each.

How Do CAB Meetings Work in Freshservice?

Freshservice provides a dedicated CAB meeting interface inside the Work Calendar. Admins schedule meetings, define agendas, and filter which change requests need review. During the meeting, the “Run Meeting” button opens the CAB workspace where members review, discuss, and vote on changes directly within the platform.

After the meeting concludes, attendees automatically receive a summary email containing all reviewed changes, discussion notes, and decisions. This creates a complete, auditable record of every CAB decision — valuable for compliance audits and post-incident reviews.

How Do You Automate Change Approval Routing in Freshservice?

Rather than manually requesting CAB approval for every change, Freshservice lets you automate approval routing based on change type, risk level, or other attributes. The approach:

1. Create a new Workflow Automator rule for the Change module.
2. Set the trigger to “Change is Created.”
3. Add a condition: for example, Change Type = Major.
4. In the action node, select “Request for Approval” and add the appropriate CAB as the approver group.
5. Define the approval rule (Everyone, Majority, etc.) and the chain rule.
6. Add downstream actions for the “Approved” branch (e.g., move to Pending Release status) and the “Rejected” branch (e.g., notify the change owner and return to Planning).

This automation ensures that every major change automatically reaches the right stakeholders for review without anyone needing to remember to initiate the process manually.

---

What Is the New Freshservice Approval Framework and What Changed in 2025?

Freshservice rolled out a significant update to its approval framework in 2025, introducing Approval Groups and Chains as a replacement for the legacy approval behavior. Understanding this change matters if you manage existing approvals or plan to build new ones.

What Did the Legacy Approval System Do Differently?

Under the old system, multiple approval requests triggered through different workflows were merged together, and the latest approval rule overrode any previously set rules. This behavior caused unpredictable outcomes when multiple workflows targeting the same ticket contained approval actions.

What Does the New Approval Framework Change?

The new framework introduces three major improvements:

1. Named Approval Groups: Each “Send Approval Mail to” action now creates a dedicated, named approval group. Groups no longer merge — each group maintains its own rule independently.
2. Approval Chains: Groups execute in sequence (or in parallel), giving admins explicit control over the order of approvals within a workflow.
3. Non-Blocking Workflow Execution: Previously, when a workflow triggered an approval, all subsequent workflows matching the same event and conditions were blocked until the approval resolved. The new non-blocking setting allows subsequent workflows to begin executing immediately, regardless of pending approval outcomes.

Freshservice’s official documentation notes that non-blocking execution “is enabled by default for new signups post May 15, 2025,” and existing accounts can enable it through Settings → Approvals → Enable the ‘Approvals node won’t block workflows’ toggle.

Feature	Legacy Behavior	New Framework Behavior
Approval groups	Merged; latest rule overrides all	Independent; each group has its own rule
Parallel workflows	Blocked pending approval outcome	Execute immediately (non-blocking)
Group naming	Not supported	Each group can be named
Chain-level rule	Not configurable	Configurable: “Set rule for approval chain as” action

---

How Do You Test and Troubleshoot Approval Workflows in Freshservice?

Building the workflow is only part of the process. Testing carefully before going live prevents approval errors from affecting real requests.

How Should You Test a Freshservice Approval Workflow?

Follow this testing checklist before activating any approval workflow in production:

• Create a test ticket or change that exactly matches your workflow’s trigger and condition criteria.
• Check the Approvals tab on the test record to confirm the correct approval groups formed, with the right approvers and rules.
• Verify the email notification that approvers receive — confirm the content, links, and reply-to-approve instructions are correct.
• Test both branches: approve the request and confirm the downstream action fires correctly. Then test rejection to confirm the notification and alternate path function as expected.
• Review the workflow execution log (available in the Workflow Automator list view) for any errors, skipped nodes, or unexpected behavior.
• Test with non-blocking execution enabled if your account uses multiple consecutive workflows that include approval actions.

What Are the Most Common Freshservice Approval Workflow Mistakes?

Avoid these frequent configuration errors:

• Overlapping workflows: Two rules targeting the same event and conditions can send duplicate approval requests. Audit all active workflows before adding new ones.
• Using “Set Approval Status as” in the same action node as “Send Approval Email to”: Freshservice’s documentation explicitly warns against this in the new framework, as it produces conflicting actions.
• Missing rejection paths: Every approval workflow needs a defined action for both the approval and rejection outcomes. Without a rejection branch, rejected requests simply stall with no notification.
• Not configuring reminders: Without reminder settings, approvers who miss the initial email can leave requests pending indefinitely.
• Skipping sandbox testing: Always validate new approval workflows in a test environment before activating them in production — especially complex change management workflows with multiple sequential approval stages.

---

What Are the Best Practices for Managing Freshservice Approval Workflows at Scale?

As your approval workflow library grows, governance becomes as important as configuration.

How Do You Keep Approval Workflows Organized and Maintainable?

• Use consistent naming conventions: For example, “[Module] – [Trigger] – [Approval Type]” — such as “Service Request – Raised – MacBook Manager + Dept Head Approval.”
• Add descriptions to every workflow: Explain the business reason, the conditions, and the expected outcome. This context proves invaluable when teammates modify workflows months later.
• Clone before modifying: Always duplicate an active workflow before making significant changes. The clone acts as an instant rollback point if the new configuration causes problems.
• Document approval chains externally: Keep a shared process document (for instance, a Zoho Projects wiki or task description) that maps every active approval workflow to its business owner, conditions, and last review date.

Which Metrics Should You Track to Evaluate Approval Workflow Performance?

Regular metric reviews help you identify bottlenecks and optimize the approval experience:

Metric	Why It Matters
Average approval response time	Identifies slow approvers or understaffed approval groups
Approval rejection rate by type	Reveals process gaps or unclear request criteria
Workflow execution error count	Highlights misconfigured conditions or missing approver assignments
Time from approval to fulfillment	Measures how efficiently downstream work executes after approval
SLA compliance on approved requests	Confirms that approval automation supports, rather than hinders, service targets

Use Freshservice Analytics to pull these metrics and review them quarterly. If approval response times consistently exceed targets, consider expanding approval groups or adding reminder escalations.

---

Conclusion

Building effective approval workflows in Freshservice transforms how your organization governs IT requests and change management. Instead of relying on manual routing, inbox-based tracking, and ad-hoc escalation, Freshservice gives every stakeholder a structured, automated, and fully auditable path from request to approval to fulfillment.

Throughout this guide, you learned how Freshservice’s approval framework operates — from the four approval rules and named approval groups to multi-level service request hierarchies and CAB-driven change management. You also explored the 2025 framework update, which introduced non-blocking workflow execution and independent approval chains, making complex multi-workflow approval scenarios more predictable and reliable than ever before.

The connection to Zoho Projects makes the overall system even more powerful. Freshservice governs the approval decision; Zoho Projects manages the downstream delivery. When a service request approval completes in Freshservice, Zoho Projects can automatically create the corresponding project, assign tasks to the right people, and track progress through to completion — closing the gap between approval and action with automation at both ends.

---

Frequently Asked Questions

---