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
    • 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
  • Key use-cases for using advanced configuration editor
  • How to Use
  • Step 1: Navigate to the Advanced Configuration Editor
  • Step 2: Select a Configuration
  • Step 3: View and Edit the JSON
  • Step 4: Add a New Configuration (Multi-Cardinality Only)
  • Important Guardrails
  • Common Use Cases
  • Reference list for Setup left nav page to configuration name in the dropdown
  • Enterprise Search
  • Ticketing Automation
  • Access Management
  • Core Platform
  • Chat Platforms, Display & Notification Configs
  • Organization Details
  • Frequently Asked Questions
Moveworks Setup

Advanced Configuration Editor

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

Identity configuration

Guided journey for indexing your users and their attributes that can be used to configure downstream skill.
Next
Built with

The Advanced Configuration Editor lets you view and edit Moveworks Setup configurations directly in JSON format. Found under Troubleshooting Tools in the left navigation bar, this power tool puts full configuration control at your fingertips — enabling bulk operations, configuration duplication, environment migration, and faster troubleshooting.

The Advanced Configuration Editor is intended for Moveworks partners and Advanced Moveworks users. We do not recommend admins use this mode as it directly modifies live configurations and can break existing functionality — use the standard UI instead.

Key use-cases for using advanced configuration editor

CapabilityDescription
Bulk OperationsUpload, replace, or copy-paste multiple configurations at once — e.g., adding 150 destinations and payload mapping in one go.
Configuration DuplicationCopy an entire configuration JSON from one instance or implementation and paste it into another, adjusting only org-specific fields.
Environment MigrationQuickly promote configurations from sandbox to production by copying JSON and updating only environment-specific values
UI FallbackAdd or edit configurations when the standard Moveworks Setup UI has issues — e.g., bypassing an overly strict UI validation bug

How to Use

Step 1: Navigate to the Advanced Configuration Editor

Go to Moveworks Setup > Troubleshooting Tools > Advanced Config Editor in the left navigation bar.

Step 2: Select a Configuration

  1. Use the Configuration dropdown to search for and select the configuration you want to view or edit.
  2. Configurations are identified by their Moveworks configuration name (e.g., TicketWorkflow, CustomDomainConfig, TicketRoutingConfig).
  3. Only a subset of configurations are available. These are vetted by the Moveworks team.
Configuration TypeBehavior
Single cardinalityDisplays a single sub-configuration directly (e.g., InfoConfig, HandoffConfig)
Multi-cardinalityDisplays a list of sub-configurations to choose from, plus a • Add new config option (e.g., TicketWorkflow with 20+ sub-configs)

Step 3: View and Edit the JSON

  1. The full JSON configuration is displayed in the editor.
  2. Make your changes directly in the JSON editor.
  3. Click Save to submit your changes.

On success: You will see a confirmation message: “Your change is now successfully saved.”

On error: The editor will display a specific error code and message. For example:

  • Error 13009 — Validation failure (e.g., display_name must contain at least 1 character)
  • Error 13002 — Deserialization failure (e.g., submitting empty or malformed JSON)

Step 4: Add a New Configuration (Multi-Cardinality Only)

For multi-cardinality configurations:

  1. Select the configuration type from the dropdown.
  2. Click + Add new config.
  3. The editor opens in create mode with a blank JSON template containing the required fields.
  4. Fill in the required fields and click Save.

Important Guardrails

GuardrailDetails
Only Moveworks Setup configurationsOnly Moveworks setup configurations are provided through this view. The configurations are sub-set and vetted by the Moveworks team as “Safe to be edited” in a JSON based view
Internal fields strippedAny fields that are internal to Moveworks are not exposed via this view or cannot be edited
No UI validationsStandard UI validations (required fields, min length, etc.) are not enforced in JSON mode — use caution.
No DSL hintsDSL validation and hints available in the standard UI are not available in JSON mode.
Bender fieldsBender fields (if applicable) must be added or modified in the long format. Please note the Moveworks Setup UI uses a short hand bender format. We absolutely do not recommend using the Advanced configuration editor for bender related fields.
No Credential visibilityThe JSON view shows a masked ID for fields where a secrets are being stored. We recommend to be extremely cautious not edit this as this might cause the connector to fail.

Common Use Cases

Use CaseHow It Helps
Replicate a ServiceNow ticketing mapper across subsidiariesCopy the full JSON config, paste it into a new tenant, and adjust only org-specific fields (assignment group IDs, custom field IDs)
Promote a Slack connector from sandbox to productionCopy sandbox JSON, paste into production, update only environment-specific values (workspace ID, OAuth references), and validate
Work around a UI validation bug blocking a go-liveBypass an overly strict UI validation (e.g., blocked non-US locale) by editing the JSON directly

Reference list for Setup left nav page to configuration name in the dropdown

Enterprise Search

Dropdown ValueSetup Left-Nav Path
KnowledgeIngestionConfigSearch -> Configure Search -> Classic Ingestion -> Internal Knowledge
KnorahConfigLookup -> Plugin Settings
DisplayVarsSetupLookup -> Lookup Configs
KnorahConfigSetupLookup -> Conference Rooms

Ticketing Automation

Dropdown ValueSetup Left-Nav Path
BackfillTicketEventsConfigTicketing -> Advanced Settings -> Ticket Event Backfill
FileTicketDestinationsConfigTicketing -> Advanced Settings -> File Ticket Destination
FileTicketTypeOverridesConfigTicketing -> Advanced Settings -> Overrides
IPAllowlistConfigTicketing -> Advanced Settings -> IP Allowlist
ITSMProviderConfigTicketing -> Advanced Settings -> ITSM Providers
ITSMProviderConfig-AdvancedSettingsTicketing -> Advanced Settings -> ITSM Providers
ITSMProvidersConfigTicketing -> Advanced Settings -> Ticket Poller Settings
ITSMProvidersConfig-AdvancedSettingsTicketing -> Advanced Settings -> Ticket Poller Settings
ITSMWebhooksConfigTicketing -> Advanced Settings -> Webhooks
ServicePortalConfigTicketing -> Advanced Settings -> Service Portal URL
TicketDestinationConfigTicketing -> Advanced Settings -> Ticket Destinations
TicketDestinationConfig-AdvancedSettingsTicketing -> Advanced Settings -> Ticket Destinations
TicketDestinationMapperTicketing -> Advanced Settings -> Ticket Destination Mapper
TicketTypesConfigTicketing -> Advanced Settings -> Ticket Types and States
TicketTypesConfig-IngestionTicketing -> Advanced Settings -> Destination Level Mapper
ITSMProvidersConfig-ConciergeTicketing -> Concierge Settings -> Advanced Settings
TicketUpdateNotificationConfigTicketing -> Concierge Settings -> Advanced Settings
TicketingActionConfig-AdvancedSettingsTicketing -> Concierge Settings -> Advanced Settings
TicketUpdateNotificationConfig-NotificationDeliveryTicketing -> Concierge Settings -> Notifications Settings
NotificationScheduleConfigTicketing -> Concierge Settings -> Notifications Settings
TicketUpdateNotificationConfig-TicketActionsTicketing -> Concierge Settings -> Ticket Actions
TicketingActionConfig-TicketActionsTicketing -> Concierge Settings -> Ticket Actions
TicketFiltersConfigTicketing -> Ticketing Settings -> Ticket Filters
MWFormConfigTicketing -> Ticketing Settings -> Rich Ticket Filing
AccessAccountIntegrationConfig-TicketingTicketing -> Ticket Interception
AccessGroupConfig-TicketingTicketing -> Ticket Interception
AccessSoftwareConfig-TicketingTicketing -> Ticket Interception
TicketRoutingConfigTicketing -> Ticket Interception
TicketingActionConfig-InterceptionTicketing -> Ticket Interception
NudgeConfig-TicketingTicketing -> Ticket Nudge Setup
TicketRoutingConfig-WorkflowsTicket Workflows -> Routing Conditions
TicketWorkflowTicket Workflows
FormIngestionConfigForms -> Advanced Settings -> Plugin Settings
FormIngestionConfig-BiddingForms -> Advanced Settings -> Plugin Settings (Bidding)
FormIngestionIntegrationConfigForms -> Advanced Settings -> Form Ingestion Advanced Mode
FormsConfigForms -> Advanced Settings -> Plugin Settings
ITSMProvidersConfig-BiddingForms -> Advanced Settings -> Plugin Settings (Bidding)
TicketingActionConfigHandoff -> Live Agent Handoff
AgentHandoffConfigHandoff -> Live Agent Handoff
MessageBrokeringConfigHandoff -> Message Brokering
HandoffConfigHandoff -> Handoff Settings
ApprovalsConfigEnterprise Approvals -> Plugin Settings
ApprovalsResourceConfigEnterprise Approvals -> Resource Settings
ApprovalsIntegrationConfigEnterprise Approvals -> Integration Settings

Access Management

Dropdown ValueSetup Left-Nav Path
AccessAccountConfigAccount Access -> Advanced Settings -> Bidding
AccessAccountIntegrationConfigAccount Access -> Plugin Settings
GroupIngestionConfigGroup Access -> Ingestion
AccessGroupConfigGroup Access -> Connector Settings
AccessGroupConfig-SkillSettingsGroup Access -> Plugin Settings
AccessSoftwareAppSoftware Access -> Software Catalog
AccessSoftwareConfigSoftware Access -> Connector Settings
NamedApprovalExpMoveworks Approvals -> Approval Workflows

Core Platform

Dropdown ValueSetup Left-Nav Path
ConnectorConfigConnectors -> Built-in Connectors
[ConnectorName]ConnectorConnectors -> Built-in Connectors (70+ individual connectors, e.g., SlackConnector, SnowConnector, JiraConnector, etc.)
BotAccessConfigUser Identity -> Bot Access
IdentityIngestionVarsUser Identity -> Import Users
IdentityServiceAccountVarsUser Identity (Service Accounts)
FileIngestionConfigIngestion
AccessAccountIntegrationConfig-ChannelChannel Resolver -> Plugin Settings
NudgeConfigChannel Resolver -> Plugin Settings
ChannelVarsChannel Resolver -> Channel Settings
CustomAttributeConfigAnalytics and Data -> Custom Attributes
BPIConfigAnalytics and Data -> Advanced Settings -> Bot Insights Settings
CustomerValueConstantsVarsAnalytics and Data -> Advanced Settings -> Analytics Value Settings
AppConfigAnalytics and Data -> Advanced Settings -> Analytics App Settings
AppDataFilterConfigAnalytics and Data -> Advanced Settings -> App Data Filter
AttributeDataSourceConfigAnalytics and Data -> Advanced Settings -> Attribute Data Source
AttributeMappingConfigAnalytics and Data -> Advanced Settings -> Attribute Mapping
UserAttributeMetadataConfigEmployee Communications -> Employee Communications
CustomDomainConfigDomains -> Domains

Chat Platforms, Display & Notification Configs

Dropdown ValueSetup Left-Nav Path
ChatVarsManage Chatbots -> Chatbots
MoveWebChatAuthConfigWeb Chatbot -> Authentication
MLSVarsMultilingual Support -> Language Preferences
CopilotDisplayVarsDisplay Configurations -> Display Settings
DisplayVarsDisplay Configurations -> Display Settings
InfoConfig-WebDisplay Settings -> Web-Form Styling
NotificationOrgConfigNotification Settings -> Notifications

Organization Details

Dropdown ValueSetup Left-Nav Path
InfoConfigTenant Settings -> General Information
SSOConfigTenant Settings -> Single Sign-On (SSO)
CustomerAlertConfigAlerts

Frequently Asked Questions

  • What happens if I submit invalid JSON?
    The editor will reject the save and display an error. For example, submitting empty JSON returns Error 13002: “Failed to save config due to precondition check: Unable to deserialize data.”
  • Are standard UI validations applied in JSON mode?
    No. UI validations such as required fields, minimum length, and DSL hints are not enforced in JSON mode. You are responsible for ensuring the JSON is valid and complete.
  • Can I create new configurations, or only edit existing ones?
    You can do both. For multi-cardinality configurations, use the + Add new config option to create a new configuration from a blank template.
  • Will the JSON structure change in the future?
    Yes, the JSON structure may change in future updates. Always refer to the current configuration schema and avoid hardcoding assumptions about field names or structure.
  • Can I update secrets or sensitive credentials through this editor?
    No. Please refrain from updating secrets or sensitive credentials via the Advanced Configuration Editor. Secrets are represented as UUIDs mapped to values stored securely — direct modification is not supported in v1.
  • Why can’t I find a specific configuration in the dropdown?
    Only approved, customer-facing configurations are shown. Internal UIVars and configurations that haven’t been approved by engineering DRIs are intentionally hidden from the dropdown.