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 Solarwinds instance ?
  • Access Requirements
  • Access Setup Walkthrough
  • Setup Overview
Access RequirementsTicketing Systems & ITSMs Access

SolarWinds Samange Access Requirements

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

Sysaid Access Requirements

Next
Built with

Why do we need access to your Solarwinds instance ?

The service account created in your Solarwinds instance will perform create, update operations on behalf of end users as well as notify end users on ticket related updates.

The Moveworks Service interacts with your Solarwinds platform so that the bot can:

  • Monitor tickets for autonomous resolution
  • Identify end users/employees
  • Create tickets for issues that require an agent’s attention
  • Reach out to an employee when a Solarwinds ticket needs the employee’s attention (via ticket comments)

Access Requirements

Moveworks need the JWT auth token to authenticate with the Solarwinds instance which is tied to the service account.

Access Setup Walkthrough

To setup a new service account user navigate to the Setup page in your Solarwinds instance and create a new user

Select the role as an administrator as in Solarwinds only users with admin license can generate an API token.

Once the user is create click on the user, click on the actions tab in the page and Generate JSON web token from the dropdown menu (Solarwinds Service Desk administrator rights required).

In the user detail page under JSON Web Token you can see the following options:

  • Copy: Copy the token to your clipboard.
  • Reset: Reset your token.
  • Delete: Delete your Token.
  • Hide Token: Minimize your token, and replaces with a Show Token link.

Click Copy and securely store the token to share with Moveworks.

Setup Overview

After setup is complete, provide the following information to your Moveworks CS team:

  • JSON Web Token
  • Service account login credentials

Provide provide ALL of the above to your Moveworks Customer Success team via encrypted email.