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
      • Configure Access Software
        • How To Guides for Access Software Plugin
        • Device Actions For Software Troubleshooting Jamf Mecmsccm Intune Munki
        • Configure Provisioning Systems
        • Configure Software Catalog
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
    • 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
  • Overview
  • Quick Navigation
  • Supported Provisioning Systems
  • System Requirements
  • Configure Connector Settings
Provision ManagementAccess SoftwareConfigure Access Software

Configure Provisioning Systems

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

Configure Software Catalog

Next
Built with

Overview

The Provisioning System configuration in Moveworks enables automated software access provisioning for your employees. This guide explains how to configure software provisioning integrations, define provisioning strategies, and customize the user experience for software access requests.

What is a Provisioning System?

A provisioning system is the identity and access management platform that Moveworks uses to automatically grant or revoke software access. When a user requests software through Moveworks, the system communicates with your provisioning platform to add the user to the appropriate groups or roles.

✨ Key Point: Moveworks supports three provisioning systems: Okta, Active Directory & OpenLDAP, and Azure AD (MS Graph). You can use any combination of these based on your organization’s infrastructure.

Quick Navigation

  • Supported Provisioning Systems
  • Provisioning Strategies

Supported Provisioning Systems

Moveworks supports three provisioning systems for software access:

SystemConnector Type
OktaOkta Connector
Active DirectoryLDAP/Active Directory (Agent) Connector
Microsoft Entra (Azure AD/MS graph)MS Graph Connector

System Requirements

For Okta:

  • Active Okta tenant with admin access
  • Moveworks Okta connector configured with API permissions
  • Group IDs for software access (alphanumeric format starting with 00g)
  • Permission to add/remove users from groups

For Active Directory (LDAP):

  • On-premise Active Directory or LDAP server
  • Moveworks LDAP (active_directory) connector configured via Moveworks Agent
  • Security group Distinguished Names (full OU path)
  • Service account with permissions to modify group memberships
  • Network connectivity from agent healthy

For Microsoft Entra (Azure AD/MS Graph):

  • Active Microsoft Entra tenant
  • Moveworks MS Graph connector configured
  • Microsoft Graph API permissions: Group.ReadWrite.All, User.Read.All
  • Security group Object IDs or Distinguished Names
  • Admin access to manage groups and users

Configure Connector Settings

Step 1: Select Connector

Specify your “Provisioning System” by selecting the correct connector, such as Okta. This is the system that our application will utilize for software provisioning.

Step 2: Post Provisioning URL

Define the URL that users will be directed to after successful provisioning. Usually, this will be a link to your selected Provisioning System’s portal, like Okta. This ensures that users know where to go after they’ve successfully requested software. E.g. https://companyname.okta.com/login/signout