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
  • Roles Required:
  • Table + Attributes Required:
  • Update Set Installation
  • Detailed Reasons for Attribute on HR Case Table:
  • Standard Fields for Ticket Actions  (Create, Comment, etc.), Support, and Debugging
Access RequirementsTicketing Systems & ITSMs Access

ServiceNow for HR Access Requirements

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

Jira Service Desk Permission (On-Prem) Access Requirements

Next
Built with

This document outlines the access required for Moveworks/ServiceNow HR Integration for ticketing.

Roles Required:

Moveworks requires the following role:

sn_hr_sp.admin- Used to ingest HR Record Producer Form Details (destination table, scripts, etc.)

Table + Attributes Required:

Moveworks also requires a custom role that grants access to the following Table APIs.

Moveworks may read the following fields, exact field names may vary based on customization done to your ServiceNow instance. If you have a custom field that is used in place of one of the out of the box fields specified below, please include access to that field when integrating with Moveworks.

Table/ API

Attributes Used

HTTP Methods Used & Use Case

/api/now/table/sn_hr_core_case

Outlined below

  • POST: Create Case, PUT: Update Case
  • GET: Retrieve Case Details

/api/now/v2/table/sc_item_produced_record

sys_id, record_key, sys_updated_by, task, sys_created_on, sys_mod_count, producer, record_table, sys_updated_on, sys_tags, sys_created_by

  • GET: Retrieve Ticket Status

/api/now/v2/table/sys_journal_field

sys_id, sys_created_on, name, element_id, sys_tags, value, sys_created_by, element

  • GET: Retrieve Ticket Comments & Work Notes

/api/now/v2/table/sys_user

sys_id, other directory attributes

  • GET: Retrieve Users

/api/now/v2/table/kb_knowledge

all

  • GET: Retrieve Knowledge articles

Update Set Installation

Click here to download and install the Moveworks ServiceNow update sets.

The Moveworks bot can respect user criteria for knowledge articles and catalog items.

To set this up, please install the Moveworks update sets into your ServiceNow non-production and production instances.

After installing the update sets, a new role called moveworks_user is added to your instance. This role will need to be assigned to the Moveworks service account.

For more information on what the update sets contain, see this document.

Detailed Reasons for Attribute on HR Case Table:

The following attributes should be granted if they exist. If they do not exist, you can omit granting the access.

Field NameAccess LevelBusiness Justification
activeREADUsed to only read active tickets when presenting back a user’s ticket statuses.
close_notesREADUsed to notify users on ticket updates when ticket is resolved
closed_atREADUsed when querying & filtering tickets
closed_byREADUsed when querying & filtering tickets
commentsREADUsed to notify users on ticket updates
descriptionREADUsed when querying & filtering tickets
detailsREADUsed when querying & filtering tickets
due_dateREADUsed when querying & filtering tickets
locationREADUsed when querying & filtering tickets
numberREADUsed when querying tickets
opened_atREADUsed when querying & filtering tickets
opened_byREADUsed when querying tickets
opened_forREADUsed when querying tickets
parentREADUsed when querying tickets
priorityREADUsed for Filtering our high priority tickets
reassignment_countREADUsed for Ticket Triage
stateREADUsed when querying tickets
sys_idREADUsed when querying tickets
sys_updated_byREADUsed when querying tickets
sys_updated_onREADUsed when querying tickets
sys_class_nameREADUsed to query the correct type of tickets
watch_listREADUsed for watcher ticket notifications
impactWRITEUsed when creating tickets
urgencyWRITEUsed when creating tickets
contact_typeWRITEUsed when creating tickets
assignment_groupWRITEUsed when creating tickets
short_descriptionWRITEUsed when creating tickets
descriptionWRITEUsed when creating tickets
opened_forWRITEUsed when creating tickets
callerWRITEUsed when creating tickets
service_offeringWRITEUsed when creating tickets
subject_personWRITEUsed when creating tickets, and showing ticket status.

Standard Fields for Ticket Actions  (Create, Comment, etc.), Support, and Debugging

Optional Fields Based on if they are used in your ServiceNow environment

  • task_effective_number - READ
  • skip_auto_assign - READ
  • skip_automatic_user_acceptance_state - READ
  • universal_request - READ
  • transferred_from - READ
  • time_worked - READ