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 Sysaid instance?
  • Production Access Permissions
  • Sysaid Authentication
  • What is this account used for
Access RequirementsTicketing Systems & ITSMs Access

Sysaid Access Requirements

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

Identity and Access Management Systems Access

Next
Built with

Why do we need access to your Sysaid instance?

The account we create in your Sysaid instance will directly perform actions to create, update, and query information about tickets & view users and knowledge.

(Optional) If you use Sysaid’s on-prem version, we’ll also need to setup the Moveworks Agent to be able to connect with your system. In this case, contact your Customer Support team to help.

Production Access Permissions

In your Production Sysaid environment, the following accounts are needed:

  • One user account (for testing & end-to-end validation) with the End User role.

  • One dedicated service account as an Administrator to read/update tickets and read users/KB articles (only admins in Sysaid are allowed to call the Sysaid API).

  • Additionally we’ll need to confirm this admin service account has the following permissions:

Please provide the username and password for both the service accounts to your Customer Success team.

Sysaid Authentication

API access for Sysaid is done through cookie-based API sessions. Moveworks will generate these using the created service account credentials.

What is this account used for

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

  • monitor tickets for autonomous resolution
  • reach out to an employee when a Sysaid 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
  • read the Sysaid user roster so that the bot can log and assign issues appropriately