Build better products with our product team.
How are we improving the product?We’re expanding access to in-bot alerts so designated recipients can receive notifications through the Moveworks Slack bot, helping teams become aware of issues without regularly checking the Alerts page.Super Admins can manage who receives notifications through Notification Settings on the Alerts page in Moveworks Setup.
We would like to request the ability for custom Agent Studio plugins to dynamically search and retrieve relevant content that has already been indexed by Moveworks.To clarify our use case, we are not requesting real-time Web search functionality such as Live Search, nor are we looking to use the built-in Enterprise Search plugin directly.Our specific use case is as follows: We have internal knowledge sources already configured and indexed in Moveworks, including: Manuals stored in Box Knowledge articles stored in ServiceNow A user submits a query to a custom Agent Studio plugin. Based on the user's query, we would like the custom plugin to dynamically search the content already indexed by Moveworks and retrieve the most relevant internal knowledge. We would then like to provide the retrieved content as context to an LLM Action, such as generate_text_action or generate_structured_value_action, so that the LLM can generate a response based on the relevant internal knowledge. Ideally, this should be possible without having to specify individual files, articles, or knowledge resources in advance within the custom plugin. In short, we would like custom Agent Studio plugins to have a mechanism to dynamically access and retrieve relevant content from the knowledge sources already indexed by Moveworks, and use that retrieved content as context for subsequent LLM Actions.This would allow custom plugins to make use of newly added or updated knowledge without requiring individual knowledge resources to be manually configured in each plugin.We understand from Moveworks Support that this capability is not currently available for custom Agent Studio plugins, so we would like to request it as a Product Idea.Thank you for considering this request.
We believe it would be beneficial to isolate individual connectors so that a failure in one does not cause a full breakdown of user ingestion. For example, recently our Okta connector (used only for proactive account unlock) experienced a failure, and this halted all user ingestion, which is primarily done through our ServiceNow connector. Ideally, an Okta failure would not prevent all user ingestion from happening. This prevented all new hires from being ingested and also caused user attributes that had been updated in ServiceNow not to be updated in Moveworks.
SummaryEnable users to apply filters in EmployeeWorks Enterprise Search before initiating a search, rather than requiring an initial search before filters become available.Current ExperienceToday users must first enter and execute a search before they can access filters to narrow the results. For users who already know the scope or type of content they want, this creates an unnecessary step and consumes an additional assist before they can perform the search they actually intended.Requested ExperienceAllow users to configure available filters before executing a search.The desired flow would be: Open Enterprise Search Select the desired filters Enter the search query Search within the selected scope Receive relevant, filtered results immediately Users should still have the option to search without applying filters first.ExampleIf a user knows they only want results from a specific source or content type, they should be able to select that filter first and then search, rather than:Search → Review results → Apply filter → Search/refine againThe preferred experience would be:Select filters → Search → Receive targeted resultsBusiness ValueThis enhancement would: Reduce unnecessary assists and interactions Help users reach relevant results faster Make Enterprise Search more intuitive and efficient Reduce searches that users already know are too broad Provide users greater control over their search scope upfront Improve the overall EmployeeWorks search experience Acceptance Criteria Users can access available Enterprise Search filters before submitting a search. Users can select one or more filters before entering or executing a query. The initial search respects all filters selected by the user. Users can modify or clear filters after results are returned. Users can continue to search without selecting any filters. Applying filters before search does not require an additional assist solely to expose filtering options.
How are we improving the product?SIEM logs can now be exported through the Data API, giving security teams access to these logs for their monitoring and audit workflows. This capability is currently in Controlled Availability.How does it work?Use Data API exports to access the following log categories:EXTERNAL_APIEXTERNAL_LDAP_APICONFIG_CHANGEPERMISSION_CHANGEAUTHENTICATIONAGENT_STUDIO_LOGUSER_TOKEN_LOGRegional AvailabilityThe capability will also be available in GovCloud.DocumentationSee SIEM Logs for log details.
How are we improving the product?Moveworks is introducing Configuration APIs to help enterprise teams move configurations safely across environments such as DEV → UAT → Production.This provides a controlled, repeatable alternative to manually recreating configuration in every organization. It also allows teams to incorporate Moveworks configuration changes into their existing source-control, review, and CI/CD processes.How does it work?Two APIs enable the configuration promotion workflow:Export API: Exports an organization’s complete configuration as a single manifest that can be stored, versioned, and reviewed.Apply API: Compares the manifest with a target organization and adds, updates, or removes configuration to bring the target into alignment.Teams can preview the proposed additions, updates, and deletions before applying them. Apply operations are validated and atomic—they either complete fully or make no changes.Technical restrictionsPromotion applies to configuration only, not customer or user data.Credentials and secrets are not included in exported manifests and must be managed separately in each organization.The target organization must pass configuration and reference validation before changes can be applied.Licensing and documentationLicensing requirements and public documentation will be added before General Availability.
How are we improving the product?Teams need a way to review configurations and investigate issues without granting permission to change settings. We’re introducing the Moveworks Setup Viewer role to separate visibility from configuration editing.Users with this role can browse configuration pages, export data, and use troubleshooting tools such as Built-in Plugin Logs, Chat Playback, Ticket Viewer, and Configuration Change History. They cannot create, update, or delete configurations or manage other users’ roles and permissions.The role applies across Moveworks Setup rather than individual skills or modules. If a user also has a higher-privilege Setup role, that role takes precedence. Troubleshooting data remains redacted by default; access to unredacted data requires the separate Moveworks Setup PII Authorized Viewer role.
How are we improving the product?Today, admins and partners have limited visibility into why forms are missing, were not indexed, or cannot be filled in the Assistant. Investigating these issues often requires assistance from Moveworks Support.Troubleshooting Hub: Forms brings ingestion health and individual-form troubleshooting into Moveworks Setup. Admins can review ingestion status and data freshness, investigate active issues with troubleshooting guidance, and inspect individual forms to understand their indexing status, fillability, required access, and Trigger Entities.The experience focuses on ingestion, form availability, and permissions. Troubleshooting search retrieval or ranking for successfully ingested forms is outside this release’s scope.
How are we improving the product?Moveworks is introducing Configuration APIs to help enterprise teams move configurations safely across environments such as DEV → UAT → Production.This provides a controlled, repeatable alternative to manually recreating configuration in every organization. It also allows teams to incorporate Moveworks configuration changes into their existing source-control, review, and CI/CD processes.How does it work?Two APIs enable the configuration promotion workflow:Export API: Exports an organization’s complete configuration as a single manifest that can be stored, versioned, and reviewed.Apply API: Compares the manifest with a target organization and adds, updates, or removes configuration to bring the target into alignment.Teams can preview the proposed additions, updates, and deletions before applying them. Apply operations are validated and atomic—they either complete fully or make no changes.Technical restrictionsPromotion applies to configuration only, not customer or user data.Credentials and secrets are not included in exported manifests and must be managed separately in each organization.The target organization must pass configuration and reference validation before changes can be applied.Licensing and documentationLicensing requirements and public documentation will be added before General Availability.
How are we improving the product?Previously, testing DSL expressions and data mappings required a separate playground and API-key setup. We’re bringing DSL Playground directly into Moveworks Setup, so admins and builders can validate rules and mappings using their existing Setup session, without external tooling.Test DSL expressions and Bender data mappers against your own JSON payloads or built-in samples, then review the output and error messages before applying them to your configuration. Payload-aware autocomplete and a searchable function reference help you write expressions, while a visual Rule Builder and AI-powered Generate Rule provide additional ways to create DSL rules.
How are we improving the product?Today, Moveworks Setup provides workflow logs for Ticketing, Concierge, Nudge, and Triage, alongside external API call logs. For other built-in plugin workflows, admins and implementation partners have limited visibility and may need help from Moveworks Support to investigate issues.We’re expanding troubleshooting log coverage in Moveworks Setup to more built-in plugin workflows. This will give admins and partners more visibility into execution outcomes and failures, helping them investigate issues independently from the same place they manage their configuration.
How are we improving the product?Today, configuring Handoff requires admins to move between Handoff Settings, Display Configurations, and Live Agent Handoff. This fragmented experience requires repeated configuration across multiple areas of Moveworks Setup.We’re consolidating these settings into one guided flow so admins can configure Handoff in a single experience, rather than navigating separate configuration pages.
Simplify getting started with EmployeeWorks through a streamlined, one-click setup experience that reduces manual configuration and helps your organization get up and running faster.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.