Recently active topics

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

The Moveworks Data API currently allows API credentials to be scoped to specific data entities, but consumers retrieving an entity can receive all fields and records available within that entity. There is currently no native mechanism to restrict API consumers to an approved subset of fields or records.For enterprise customers, particularly those using Data API data for analytics and reporting, this can result in sensitive or personally identifiable information being exposed to consumers even when it is not required for their use case.We would like Moveworks to provide fine-grained access controls for Data API credentials, allowing administrators to control not only which entities an API credential can access, but also which fields and records can be returned.Proposed capabilitiesWhen creating or managing a Data API credential, administrators should be able to configure: Entity-level access Continue supporting selection of permitted Data API entities. Field/column-level access Define

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.

Hi Community,I’m interested in learning more about the controls available to customers for fine-tuning the conversational experience in Moveworks, across Slack, Microsoft Teams, and the web experience.As we expand the number of use cases and agents available through Moveworks, we’re looking at the experience beyond just answer accuracy …. specifically, how the bot communicates and interacts with employees.For example, there may be situations where we want to influence things such as:Response length and level of detail Tone and conversational style Use or expansion of acronyms Formatting and structure of responses Follow-up questions and clarification behavior How frequently the bot asks for feedback How references, actions, or help options are presented Consistency of the experience across Slack, Teams, and webWe’ve seen that some conversational behaviors can be adjusted by the Moveworks team. For example, we recently had a change implemented to minimize the use of acronyms and expand/

As a Moveworks administrator, I would like the ability to export the list of users with platform access directly from the Roles & Permissions page into a CSV and/or PDF format. I would also like the option to export the data from the permissions logs tab of Moveworks Setup.Today, administrators can view platform users and their assigned roles within the Roles & Permissions interface, but there is no straightforward way to export this information for governance, audit, access review, and compliance reporting purposes. As a result, organizations must manually gather user access information or submit support requests to obtain a complete inventory.

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

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.

Alertsページに、Box連携関連のアラートを追加していただきたいです。

DataCrawlingのログ、Alertsのログの内容をAPI経由で取得可能にしていただきたいです。

Moveworks Analytics currently shows user inputs and bot responses in plain text. While this level of visibility is extremely helpful for developers investigating unexpected bot behavior or addressing negative user feedback, exposing raw conversation text can create privacy and compliance concerns.Submitting this as a proposal to introduce native, configurable data redaction and masking capabilities within the Moveworks platform for raw interaction logs and analytics dashboards.Suggested capabilities would include:Built in regex based and AI driven entity detection to automatically identify and redact common sensitive information, such as salary details, performance ratings, and similar confidential data.The ability for tenant administrators to define custom regex patterns, keywords, or rules tailored to their organization’s specific privacy and compliance requirements.

It would be great if similar capability explained in this article Forms | Moveworks is also available with Salesforce integration for customers that are using Salesforce as their CRM

I feel that above update under “related topics” created additional challenges from data privacy perspective. We need to have a way to configure that for some analytics users, such identifiable information like e-mail address are not accessible through “view all interactions” button. Our employees may share sometimes things that are little sensitive and allowing everybody having access to Analytics accessing it and then link given interaction to individual person is just not right. I feel that this relates to another idea Permissions to restrict Interaction data in Bot analytics | Community . Permissions on Analytics must be much more granular and configurable so that people get access to the data they need and not to everything or nothing.