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
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
      • Duo Access Requirements
      • PingID MFA Access Requirements
    • 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
  • Duo Security Access Needs
  • Why do we need access to your Duo instance?
  • Admin API access needed
Access RequirementsMulti-Factor Authentication (MFA) Systems Access

Duo Access Requirements

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

PingID MFA Access Requirements

Next
Built with

Duo Security Access Needs

Why do we need access to your Duo instance?

The Moveworks service interacts with your Duo instance to help employees associate their Duo factor with their mobile device, and to help them create a bypass code to log in when their device is unavailable. Specifically, Moveworks takes the following actions in your Duo instance. Moveworks:

  • retrieves employee records from Duo based on their email addresses
  • creates Duo activation URLs for employees
  • instructs Duo to send employees activation codes via SMS

Admin API access needed

Moveworks requires credentials for the Admin API in your Duo instance to view reporting information and perform user-initiated MFA resets. Follow the steps below to set this up:

  1. Make sure your Duo Admin API is activated as explained in the Duo documentation at https://duo.com/docs/adminapi
  2. Make sure the Duo Admin API has been granted the following permissions:
    • Grant read information
    • Grant read resource
    • Grant write resource
  3. Use a secure communications channel to share your Duo Integration key, Secret key,and Duo API hostname with your Moveworks Customer Success representative.