For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
      • ServiceNow Access Requirements
      • ServiceNow for HR Access Requirements
      • Jira Service Desk Permission (On-Prem) Access Requirements
      • Moveworks Jira Application (for Jira Cloud)
      • Jira Service Management (Cloud) - Access Requirements
      • Zendesk Access Requirements
      • Freshservice Access Requirements
      • Freshdesk Access Requirements
      • Salesforce Access Requirements
      • BMC Remedy/Helix Access Requirements
      • BMC Remedyforce Access Requirements
      • Cherwell Access Requirements
      • Ivanti Service Manager Access Requirements
      • ManageEngine (Cloud) Access Requirements
      • ManageEngine (On-Prem) Access Requirements
      • SolarWinds Samange Access Requirements
      • Sysaid Access Requirements
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
    • Knowledge Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • Why do we need access to your Freshservice Instance?
  • Freshservice Permissions
  • What is this account used for:
  • Access Requirements
  • 1. Create Custom Moveworks Admin Role
  • 2. Create Service Account
  • 3. Connector Configuration
  • Service account in test/dev
Access RequirementsTicketing Systems & ITSMs Access

Freshservice Access Requirements

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Freshdesk Access Requirements

Next
Built with

Why do we need access to your Freshservice Instance?

The bot will directly perform actions in Freshservice to create, update, and query information about tickets.

Freshservice Permissions

The Moveworks service interacts with your Freshservice platform so that the bot can:

  • monitor tickets for autonomous resolution;
  • reach out to an employee when a ticket needs the employee’s attention;
  • create tickets to log issues the bot has resolved autonomously;
  • create tickets for issues that require an agent’s attention;
  • load Freshservice forms so that the bot can serve them to employees; and
  • read the Freshservice user roster so that the bot can log and assign issues appropriately.
  • read and index knowledge base articles to serve to users in your Moveworks bot.

What is this account used for:

A dedicated service account in Freshservice allows the Moveworks service to read and update tickets, and read users, forms, and knowledge articles.

Access Requirements

1. Create Custom Moveworks Admin Role

To grant the necessary roles, Agent Role titled “Moveworks Admin” and check the following boxes in the following two sections under Permissions and Scope:

  • View Tickets
    • Send reply to a ticket
    • Edit ticket properties
    • Create and Edit Tasks in Tickets
    • View or Edit time entries
      • Edit everyone’s time entries
    • Scope: Global Access
  • Administration
    • Perform Operational Admin actions
      • Manage Agents
      • View Requesters
        • Assume Requester Identity
      • View Department
      • Create/Edit Service Items/Service Category
  • Solutions
    • View Solutions Tab
      • Manage Solution Categories & Folders

2. Create Service Account

Create a new Full-Time agent account for the Moveworks bot and assign the “Moveworks Admin” role. Please note that the timezone for this account should be: (GMT+00:00) UTC

3. Connector Configuration

Leverage the following details to configure your connector in Moveworks Setup.

  • API key of this account
  • Freshservice domain/URL (i.e. https://customer.freshservice.com)
    • Even if you have a custom CNAME, Moveworks requires the actual domain for the integration.

Service account in test/dev

If you have a Freshservice sandbox instance, replicate the above steps to create a service account in the sandbox. Otherwise, create a test group named “Moveworks - test” in your Freshservice instance to utilize for testing.