Skip to main content

Get Started

The roadmap, product ideas, and product plans are subject to change without notice. These plans may be refined, updated, or revised from time to time, based on customer input and market conditions. The plan described herein is provided solely for information purposes, and is not a commitment, promise, or legal obligation to deliver any material, code, or functionality.

Share your feedback in our Product Ideas Portal

Welcome to the Moveworks Product Ideas Portal!We are committed to listening to and incorporating your feedback to our Moveworks Product Roadmap. What...

    Filter by idea status

    Filter by product

    1344 Ideas

    Back to top of the list
    Jared
    JaredInspiring

    Feature Request: Analytics for Proactive (“Pushed”) Bot Communications2. On Roadmap

    Overview Currently, the platform’s analytics focus on user-initiated interactions with our Moveworks bot. However, as customer bots evolve to be more proactive—sending notifications and updates without direct user prompts—we lack visibility into the reach and effectiveness of these communications. To better understand the impact of bot-initiated messages, we propose the addition of analytics for proactive communications. This would provide insights into what types of messages are being sent, how frequently, and how users are engaging with them. Proposal: Implement Analytics for Bot-Initiated Messaging We request a new analytics capability to track and analyze any communication that originates from the bot, including but not limited to:• System-generated notifications (e.g., password reset alerts)• Employee communications tool messages• Creator Studio-initiated messages• Concierge or plugin-based notifications (e.g., ITSM status updates, comments)• External integration notifications (e.g., ITSM approval workflows) Key Metrics & Capabilities Requested:1. Message Volume Tracking – How many bot-initiated messages are being sent over time?2. Message Source Breakdown – Categorization by system, integration, or trigger type.3. Recipient Insights – Who is receiving these messages? Are certain groups more (or less) engaged than others?4. Engagement Metrics – How do users interact with bot-initiated messages? (e.g., click rates, dismissals, response rates)5. Impact Measurement – Correlation between notifications and user actions (e.g., did a status change notification lead to a follow-up inquiry?). Benefits:• Visibility – Understand the scale and scope of bot-initiated communications.• Optimization – Identify which messages are effective and refine strategies accordingly.• User Experience Improvement – Reduce notification fatigue by analyzing engagement trends.• Data-Driven Decision Making – Leverage insights to enhance proactive support efforts. By implementing analytics for proactive bot messaging, we can ensure that these communications are both meaningful and effective, ultimately improving the best possible user experience and the value of the Moveworks bot.

    18
    Jared
    1 month ago
    willmurphyCommunity Manager

    Minor ML Update: Prevent duplicate plugin actions6. Delivered

    Fixed a GPT-5.4 issue where background (asynchronous) plugin actions could sometimes run twice. The model now correctly waits for results instead of re-triggering the same action.

    2
    1 month ago
    willmurphyCommunity Manager

    GPT 5.4 – Basic Release6. Delivered

    Updating our Reasoning Engine to GPT 5.4.

    1
    1 month ago
    Aishwarya ParthasarathiNew Participant

    Assign a Conversation Topic to Employee Communications interactions (e.g., "Employee Communications") to exclude them from Analytics gap reporting1. New

    Employee Communications campaign interactions (e.g., button clicks like "Good to know!") currently do not have a Conversation Topic assigned, which causes them to log with a <nil> value in the Conversation Topic field.In Analytics, this is inflating the <nil> Topic bucket in gap/intent-failure reporting — these interactions are being counted as unresolved or ambiguous intents (or in some cases appearing to overlap with feedback-related records), when in reality they are simply acknowledgment button clicks tied to Employee Comms campaigns. This isn't limited to "Good to know!" — any Employee Comms campaign button (e.g., "Reclaim my license" for a license-reclaim campaign) would log the same way, since none of these interactions currently receive a Conversation Topic.Request: Assign a dedicated Conversation Topic value (e.g., "Employee Communications") to all Employee Comms campaign interactions, regardless of the specific button/CTA text used. This would let customers reliably filter/exclude these interactions from gap analysis and other Analytics reporting, rather than having them fall into <nil> and skew intent-failure metrics.

    0
    1 month ago
    nicolacucinellaNew Participant

    Add horizontal scroll/slider for open CA, CP, and Actions tabs in Agent Studio4. Future Consideration

    Hi Moveworks Community,I’d like to suggest a usability improvement for Agent Studio.When working with multiple open items — such as Conversation Actions, Conversation Processes, and HTTP Actions — the top tab bar can quickly run out of space. Once many tabs are open, it becomes difficult to navigate between them because there doesn’t seem to be a clear way to scroll horizontally through all open tabs.Would it be possible to add a horizontal slider, scrollbar, or another tab navigation mechanism at the top, so users can easily move across all open CA, CP, and Action tabs?This would be especially helpful when building or debugging complex workflows with many related components open at the same time.Thanks!

    2
    Kevin Mok
    1 month ago
    mandarmarkandeyaNew Participant

    Subject: Feature Request: Proactive Health Monitoring & Credential Alerting Dashboard3. Existing Functionality/Native Skill

    Description: Dear Team,I would like to understand whether Moveworks currently provides any native capabilities within the Control Center, or via API, for the following monitoring and alerting requirements. Additionally, if any of these capabilities are already available, please let us know whether they are currently being utilized by any customer.1. Outage Monitoring and VisibilityOutage Notifications: Immediate alerts when the bot, or any of its critical connected integrations, experiences downtime.Root Cause Visibility: Detailed logs indicating what failed, when the outage started, and which specific service, system, or connector was impacted.Historical Uptime Tracking: Access to historical uptime data and incident logs for reporting and audit purposes.2. Integration Credential Expiration AlertsServiceNow: Proactive notifications (for example, 30/15/7 days in advance) for expiring service account passwords or API tokens.Microsoft Graph: Expiration monitoring for Azure AD / Entra ID client secrets and tokens used by the bot.3. Certificate and Key Lifecycle ManagementAWS Certificates: Monitoring and alerting for AWS infrastructure certificates, specifically in the Corning environment.JWT and JWKS Keys: Alerts for upcoming expiration of JSON Web Tokens (JWTs) or keys used for custom API authentication and SSO.4. Alerting and Notification ChannelsThe ability to route these notifications through preferred enterprise channels, such as:Automatic ITSM incident creationEmail notifications to the admin teamWebhook-based alerts to Slack or Microsoft TeamsRequest for ClarificationCould you please confirm:Whether any of the above capabilities are currently available natively within Moveworks Control Center;Whether they can be accessed, configured, or exposed via API;Whether any customers are currently using these capabilities; andIf not currently available, whether this can be considered a formal feature enhancement request for the product team.Thank you for your support. I look forward to your guidance.

    2
    Kevin Mok
    1 month ago
    MshaulNew Participant

    Integrate Employee Comms into Content Interface for Chat Recall1. New

    Currently our company uses content ingestion, etc. for chat, but we also use the Employee Comms feature to send out notifications/announcements to our end users in Teams. It would be ideal if anything sent through Employee Comms could become part of the Knowledge/Content within MW so that previous announcements, etc. could be accessible through chat. Specifically, when reviewing transcripts from end user conversations, I see patterns where end users ask follow up questions about specific Employee Comms/Announcements and Moveworks chat does not innately understand or have knowledge of those announcements as they function as their own “Product” within MW suite.It would be great if an end user could query those Comms and get information/answers returned in chat rather than Moveworks telling them they were unable to find an answer. We have received feedback indicating that the end users don’t understand why they would be receiving Notifications/Comms in their MW chat if they could not then ask follow up questions, etc. about that content. I think linking these products in some way would make the experience more user friendly.

    0
    1 month ago
    JishnuEmployee

    Troubleshooting Hub: On-Prem Agents4. Future Consideration

    What’s changing?Moveworks is introducing a dedicated On-Prem Agents experience in the Troubleshooting Hub within Moveworks Setup. It will give admins a central place to monitor agent availability, understand the health of connected on-premises systems, and investigate issues affecting employee requests.The experience will include:Agent health overview: See which on-prem agents are connected or disconnected and identify when deployment redundancy may be at risk.System health monitoring: Review connection health for configured LDAP and REST-based systems, including systems currently experiencing failures.Active issues and alerts: Surface important agent and system connection problems with clear impact, status, and recommended next steps.These changes are designed to help admins detect on-prem connectivity issues earlier, investigate failures more efficiently, and restore affected integrations with less reliance on Moveworks Support.

    0
    1 month ago
    rahulthakur
    rahulthakurCommunity Manager

    Troubleshooting Hub: Users2. On Roadmap

    What’s changing?Moveworks is introducing a dedicated Users experience in the Troubleshooting Hub within Moveworks Setup. It will give admins and partners a central place to monitor user identity ingestion and investigate issues without switching between multiple tools or relying on Moveworks teams for routine diagnosis.The experience will include:Ingestion health at a glance: See the latest ingestion status, fetched and indexed user counts, and scheduled run information.User-level investigation: Search for individual users and understand why a user may be missing, excluded, or dropped during ingestion.Clear issue identification: Surface connector, configuration, processing, and partial-ingestion issues affecting user identity data.Guided troubleshooting: Review customer-friendly explanations, likely root causes, recommended actions, and links to relevant configurations.Centralized workflow: Move from identifying an ingestion problem to investigating and resolving it within one experience in Moveworks Setup.These changes are designed to help admins and implementation partners validate that user data is current and complete, identify ingestion problems earlier, and resolve common issues with less reliance on Moveworks Support.

    0
    rahulthakur
    1 month ago
    kyril.remillard
    kyril.remillardCommunity Manager

    Triage Simplification2. On Roadmap

    What’s changing?Triage configuration is moving into a single, guided experience in Moveworks Setup. Instead of configuring metadata, fields, model training, rollout controls, and output guardrails across disconnected pages, admins will be able to manage the Triage setup journey in one place.The simplified experience will include:Unified setup journey: Configure prerequisites, choose fields, train the model, and manage outputs through one guided flow.One source of truth for shared settings: Manage rollout mode, delivery method, ticket eligibility, and analytics settings without duplicating configuration across multiple pages.Inline validation and safer defaults: Review ticket scope before training and use built-in guardrails to prevent invalid lookback windows or confidence settings.Clearer model controls: Set confidence thresholds, rollout behavior, allowlists, blocklists, and default values after reviewing model performance.Prediction insights: Use visual insights to understand model quality and make informed decisions about which predictions to allow or block.Optional overrides: Add deterministic heuristic rules only when needed, rather than configuring them for every Triage field.These changes are designed to reduce configuration errors, shorten setup cycles, and make Triage easier for admins and implementation partners to configure, validate, and maintain without extensive Moveworks assistance.

    0
    kyril.remillard
    1 month ago
    JishnuEmployee

    Enhanced New User Identity Journey4. Future Consideration

    Admins can configure and validate user identity faster with more flexible source mappings, preconfigured Microsoft Graph settings, expanded overrides, and richer test-user previews.

    0
    1 month ago
    rahulthakur
    rahulthakurCommunity Manager

    Guided Setup Journey6. Delivered

    How are we improving the product?New Moveworks admins can now follow a guided journey from the Moveworks Setup Overview page. Instead of navigating the platform without a clear starting point, admins receive an organized sequence of foundational setup activities with the context and resources needed to get started.The Getting Started guide helps admins understand what to configure, how long each activity may take, and where to find detailed guidance—making initial setup easier to navigate and reducing uncertainty during onboarding.How does it work?Admins in organizations that are still onboarding see a Getting started? banner on the Moveworks Setup Overview page.Opening the guide displays the recommended setup journey organized into sections and steps.Each step includes a description, an estimated completion time, and a link to relevant documentation.Admins can select Start to go directly to the appropriate configuration area in Moveworks Setup.Section navigation helps admins move through the journey and understand the broader setup process.Licensing restrictionsThis capability is available to customers with access to Moveworks Setup. Users must have the appropriate administrative permissions to access and complete configuration activities.Technical restrictionsThe Getting started? banner is shown only for organizations that are in the onboarding stage.The guide does not currently track or display completion status for individual setup steps.The guide provides recommended navigation and resources; the exact configuration work and prerequisites vary by organization and integration.DocumentationLearn more about the guided setup journey in the Moveworks Setup Getting Started Guide.

    0
    rahulthakur
    1 month ago
    rahulthakur
    rahulthakurCommunity Manager

    Expanded Configuration Deletion6. Delivered

    How are we improving the product?Admins can now delete 10 additional configuration types directly in Moveworks Setup. This makes it easier to clean up test or unused configurations after implementations, migrations, and environment cutovers without filing a support request.The expanded deletion experience includes dependency checks where applicable and configuration-specific warnings to help admins understand the impact before completing a permanent action.How does it work?Self-service deletion is available for these additional configuration types:ConnectorsSSOChatbotUser IdentityFormsSoftware AccessLive Agent HandoffPermission RulesMirror PermissionsChannel ResolverOpen the supported configuration in Moveworks Setup and select Delete.Review the warning describing the impact of deleting that configuration.When applicable, Moveworks checks whether other configurations depend on it. If references exist, deletion is blocked until those dependencies are removed.Confirm the deletion to permanently remove the configuration.Licensing restrictionsThis capability is available to customers with access to Moveworks Setup. Users must have the appropriate administrative permissions to manage and delete configurations.Technical restrictionsDeletion is permanent and cannot be undone.User Identity and SSO configurations can only be deleted in non-live organizations.The default Web chatbot cannot be deleted.Connectors with active configuration dependencies cannot be deleted until those references are removed.After deleting a connector, its name cannot be reused.Additional restrictions may apply depending on the configuration type and its references.DocumentationLearn how configuration deletion works, including supported types, dependency checks, and safeguards, in the Configuration Delete documentation.

    0
    rahulthakur
    1 month ago
    rahulthakur
    rahulthakurCommunity Manager

    Self-Serve Validation Failure Alerts6. Delivered

    How are we improving the product?Validation failures can block user and form ingestion when Moveworks detects an unexpected data change. Previously, admins and implementation partners had limited context about what failed and often needed help from Moveworks teams to validate expected changes.Self-Serve Validation Failure Alerts bring detailed, actionable alerts into Moveworks Setup. Admins and partners can understand the affected resource, review why validation failed, and resolve supported failures directly—reducing implementation delays and reliance on support.How does it work?When a supported user or form ingestion validation fails, Moveworks creates an alert in Moveworks Setup with details about the change and its impact.The admin or partner reviews the alert and determines whether the data change was expected.For supported expected changes, they can override the validation failure, provide a justification, and confirm the action.If the change was unexpected, they can use the troubleshooting guidance to identify and fix the underlying configuration, permission, credential, or source-data issue.Override actions are recorded for auditability, and future validation runs use the accepted data as the new baseline.Licensing restrictionsThis capability is available to customers with access to Moveworks Setup. Users must have the appropriate administrative permissions to review and resolve alerts.Technical restrictionsThe initial self-serve override scope covers supported validation failures for user identity and forms ingestion.Not every validation failure can be overridden. Alerts that indicate unsafe or invalid data must be corrected through troubleshooting.An override confirms that the detected change is expected and cannot restore the previously indexed data.DocumentationLearn how to investigate validation alerts and resolve common causes in the Moveworks Setup Alerts Troubleshooting Guide.

    0
    rahulthakur
    1 month ago
    colemanCommunity Manager

    Adaptive Thinking2. On Roadmap

    How are we improving the Assistant’s behavior?Moveworks is introducing a lightweight model path for low-touch interactions such as “Hi”, “What’s your name?” or “Thanks”. These queries can be answered directly without calling tools, improving time to first response while preserving the full reasoning and tool-use path for more complex requests.Technical RestrictionsNone.DocumentationNo help-site documentation is currently available.Release DatesFrontier: October 19, 2026 Standard: October 22, 2026 Basic: October 27, 2026

    0
    1 month ago
    andrewwhitleyInspiring

    Version Control for Agent Studio6. Delivered

    Having multiple environments is great, but if we deploy a change and there is an issue, being able to quickly see what changed and also restoring a previous version would be instrumental.

    10
    1 month ago
    anayak

    ToolSmith7.0 Duplicate

    How are we improving the product?Building enterprise automations still requires significant manual work. Developers must translate a business need into Agent Studio building blocks, research APIs, configure authentication, map data, wire dependencies, and test the result.ToolSmith changes the job from assembling everything by hand to directing and reviewing the build. Describe the outcome you want in plain language, review ToolSmith’s proposed plan, and approve it before ToolSmith creates or updates anything.ToolSmith can help developers build new plugins, edit existing plugins, and debug failing plugins—all through a guided conversation in Agent Studio.How does it work?Describe the outcome. Start with the business result, intended users, required inputs, and what success should look like.Research and reuse. ToolSmith examines relevant documentation and the assets available in your organization. It reuses existing assets when possible and asks before changing them.Review and steer the plan. ToolSmith proposes an implementation plan that you can revise in normal language. Nothing is built until you explicitly approve it.Build with visible progress. ToolSmith executes the approved work in dependency order and reports progress and operation results in the conversation.Configure credentials securely. When a connector needs credentials, ToolSmith presents a secure configuration card. Credentials are not pasted into chat or stored in the ToolSmith conversation.Test and refine. Test the result, describe changes conversationally, and let ToolSmith update the relevant assets.Resume later. Your conversation preserves its plan, results, and pending credential requests so you can leave and return.What can ToolSmith work with during controlled availability?ToolSmith supports create, read, and update workflows for:HTTP, Script, and Compound ActionsConnectors, including HTTP and MCP connectorsPluginsConversational ProcessesData TypesStatic and Dynamic ResolversListenersToolSmith can also open an existing plugin so you can describe a change in plain language, review the proposed edits, and test the updated plugin in the same session. If a plugin is failing, you can point ToolSmith at the issue so it can investigate the root cause and propose a fix.Licensing informationLicensing information will be made available closer to controlled availability.Technical restrictions and known limitationsToolSmith cannot delete assets during controlled availability. This guardrail helps prevent accidental removal of a developer’s work.ToolSmith’s speed and accuracy vary depending on the third-party systems and APIs involved.ToolSmith performs best when a plugin involves no more than two third-party systems. More complex, cross-system workflows may take longer or require more developer guidance.ToolSmith conversations cannot currently be shared with other users.Builders should review and test all created or updated assets in a non-production environment before publishing them.Interested in ToolSmith?Upvote this product idea and leave a comment describing what you want to build, edit, or debug with ToolSmith.

    3
    sidverma
    1 month ago
    sidverma
    sidvermaCommunity Manager

    ToolSmith5. Controlled Availability

    How are we improving the product?Building enterprise automations still requires significant manual work. Developers must translate a business need into Agent Studio building blocks, research APIs, configure authentication, map data, wire dependencies, and test the result.ToolSmith changes the job from assembling everything by hand to directing and reviewing the build. Describe the outcome you want in plain language, review ToolSmith’s proposed plan, and approve it before ToolSmith creates or updates anything.ToolSmith can help developers build new plugins, edit existing plugins, and debug failing plugins—all through a guided conversation in Agent Studio.How does it work?Describe the outcome. Start with the business result, intended users, required inputs, and what success should look like.Research and reuse. ToolSmith examines relevant documentation and the assets available in your organization. It reuses existing assets when possible and asks before changing them.Review and steer the plan. ToolSmith proposes an implementation plan that you can revise in normal language. Nothing is built until you explicitly approve it.Build with visible progress. ToolSmith executes the approved work in dependency order and reports progress and operation results in the conversation.Configure credentials securely. When a connector needs credentials, ToolSmith presents a secure configuration card. Credentials are not pasted into chat or stored in the ToolSmith conversation.Test and refine. Test the result, describe changes conversationally, and let ToolSmith update the relevant assets.Resume later. Your conversation preserves its plan, results, and pending credential requests so you can leave and return.What can ToolSmith work with during controlled availability?ToolSmith supports create, read, and update workflows for:HTTP, Script, and Compound ActionsConnectors, including HTTP and MCP connectorsPluginsConversational ProcessesData TypesStatic and Dynamic ResolversListenersToolSmith can also open an existing plugin so you can describe a change in plain language, review the proposed edits, and test the updated plugin in the same session. If a plugin is failing, you can point ToolSmith at the issue so it can investigate the root cause and propose a fix.What’s next for ToolSmith?Available nowGuided MCP server and connector setup. ToolSmith guides builders through creating and configuring MCP servers and connectors, including secure credential collection.Planned for November 4, 2026Refreshed ToolSmith workspace. Clearer plans, assets, and progress make it easier to understand what ToolSmith is doing and what happens next.Stop and redirect an in-progress build. Builders can interrupt current work and steer ToolSmith toward a different approach without starting over.Submit feedback directly in chat. Builders can report issues and share feedback without leaving the ToolSmith conversation.Clearer errors and recovery. More useful error explanations and better recovery from failed or stalled builds.Faster, more reliable long-running builds. Improvements to execution reliability and progress for complex builds that take longer to complete.Planned by October 16, 2026Test plugins and conversational flows inside ToolSmith. Builders can test generated plugins and conversational processes without leaving the ToolSmith workspace.Planned by October 31, 2026Automatically approve minor plan changes. ToolSmith can continue through small, low-risk adjustments without repeatedly asking for approval.Planned for December 2026Improved editing and debugging of existing plugins. A stronger experience for finding an existing plugin, proposing changes, diagnosing failures, applying fixes, and retesting.Planned for Q1 2027Action and Connector Catalog for discovery and reuse. Builders can more easily find approved actions and connectors, understand what already exists, and reuse assets instead of creating duplicates.Dates and scope may change as we incorporate Controlled Availability feedback.Licensing informationDuring controlled availability, ToolSmith is available without an entitlement check. To continue using ToolSmith after controlled availability, customers must be entitled through EmployeeWorks or Moveworks Standalone. ToolSmith is not included with AI Native, Heritage, or Moveworks Essentials packages.Technical restrictions and known limitationsToolSmith cannot delete assets during controlled availability. This guardrail helps prevent accidental removal of a developer’s work.ToolSmith’s speed and accuracy vary depending on the third-party systems and APIs involved.ToolSmith performs best when a plugin involves no more than two third-party systems. More complex, cross-system workflows may take longer or require more developer guidance.ToolSmith conversations cannot currently be shared with other users.Builders should review and test all created or updated assets in a non-production environment before publishing them.Interested in ToolSmith?Upvote this product idea and leave a comment describing what you want to build, edit, or debug with ToolSmith.

    0
    sidverma
    1 month ago
    colemanCommunity Manager

    User consent authentication for on-premises systems2. On Roadmap

    What are we improving?Employees can use Moveworks with internal applications that require individual user authorization, even when those applications and identity providers are only accessible from within the company network.User consent authentication lets each employee connect their account and allows Agent Studio integrations to act with that employee’s existing permissions. This extends delegated authentication to private, on-premises systems without requiring customers to open an inbound connection to their network.Note: This works for both native Tool Studio plugins as well as MCP servers you bring. How does it work?The experience starts with a familiar Connect action. The employee signs in to the organization’s identity provider and grants consent. Moveworks then uses the employee’s authorized access when the integration calls the internal application.Requests that must reach the private application or identity provider are routed through the existing Moveworks on-premises agent. The agent maintains an outbound connection to Moveworks, makes the request from inside the customer network, and returns the response through the same protected channel.The main authorization flows use this route:Exchanging the employee’s one-time authorization code for access tokens Calling the internal application with the employee’s authorization Refreshing access when a token expires Revoking access when the employee disconnects the integrationThe initial browser authorization remains direct because the employee’s browser is already connected to the corporate network or VPN.How is authentication data protected?OAuth client secrets stay in the on-premises agent configuration and do not leave the customer network. User tokens are encrypted by the agent before leaving the network and are decrypted only by the agent when they are needed for an authorized internal request.Moveworks stores and forwards the agent-encrypted values without access to their plaintext contents. Existing encryption at rest provides an additional layer of protection while the tokens are stored.What does this unlock?Organizations can build Agent Studio integrations that combine user-level authorization with systems that cannot be reached from the public internet. Employees keep the permissions already defined by the internal application rather than relying on a shared service account.Examples include internal calendar, productivity, IT, finance, and business applications that support OAuth 2.0 but are accessible only from the corporate network.What is required?A supported Moveworks on-premises agent must be deployed and connected. The internal application and identity provider must support a compatible OAuth 2.0 authorization-code flow. The integration must be configured to route the applicable authentication and API requests through the on-premises agent. Employees must be connected to the corporate network or VPN when the initial authorization page is available only internally. Customer administrators must configure the required service and OAuth client information in the agent.Are there technical considerations?The first authorization step relies on the employee’s browser being able to reach the internal identity provider. Organizations with multiple agent instances must configure them consistently so authentication requests can be handled reliably.Support for nonstandard OAuth requirements—including mutual TLS, private-key client authentication, or other custom identity-provider behavior—should be validated during integration setup.AvailabilityGeneral Availability is planned for mid-November.

    0
    1 month ago
    colemanCommunity Manager

    Permissive Log Redaction for Agent Studio6. Delivered

    How are we improving the product?Standard log redaction protects sensitive information, but it can also hide request and response details that developers need to troubleshoot HTTP actions. Permissive Log Redaction gives Agent Studio admins a more flexible option: preserve useful payload details in logs while continuing to redact header values.This helps development teams diagnose integration failures faster, reduce trial-and-error during testing, and better understand how an HTTP action behaved.How does it work?A super admin can enable Permissive Log Redaction as a security setting in Moveworks Setup. When enabled, Agent Studio logs use value redaction for HTTP headers rather than applying standard redaction to additional parts of the request and response.Developers can then inspect more of the logged HTTP action details, including request and response payload information, when debugging integrations.Licensing restrictionsPermissive Log Redaction is available as an Agent Studio security setting. Contact your Moveworks account team if you have questions about availability for your environment.Technical restrictions and security considerationsEnabling this setting increases the amount of request and response data that may appear in logs. Sensitive information included outside HTTP headers—such as an access token placed in a request body—may be logged.Before enabling Permissive Log Redaction, customers should review how their integrations handle credentials and sensitive data, ensure secrets are passed through headers where appropriate, and confirm that the additional logging aligns with their security and compliance requirements.DocumentationLearn more about log redaction in Agent Studio: Log redaction.

    0
    1 month ago
    saloniEmployee

    Live Agent Chat in EmployeeWorks7.0 Duplicate

    How are we improving the product?EmployeeWorks users can start a live agent conversation directly from the Live Agent Chat app under My Apps, without leaving the Assistant experience.How does it work?The app opens an inline form where the user can describe their issue. After submission, EmployeeWorks creates a dedicated Live Agent Chat thread and displays handoff status and estimated wait-time updates.When an agent joins, users see the agent's name, photo, and messages directly in the thread. Attachments are available during the active session, and users can exit the live chat at any time and return to the Assistant.Technical restrictionsAvailable only in EmployeeWorks.Live Agent Chat must be configured for the organization.Automatic domain prediction and multi-queue routing are not included in the initial release.The initial experience starts a new thread and does not send prior Assistant conversation history to the live agent.

    1
    jmcginley
    1 month ago
    jmcginley
    jmcginleyCommunity Manager

    Live Agent Chat in EmployeeWorks WebApp5. Controlled Availability

    How are we improving the product?EmployeeWorks users can start a live agent conversation directly from the Live Agent Chat app under My Apps, without leaving the Assistant experience.How does it work?The app opens an inline form where the user can describe their issue. After submission, EmployeeWorks creates a dedicated Live Agent Chat thread and displays handoff status and estimated wait-time updates.When an agent joins, users see the agent's name, photo, and messages directly in the thread. Attachments are available during the active session, and users can exit the live chat at any time and return to the Assistant.Technical restrictionsAvailable only in EmployeeWorks. Live Agent Chat must be configured for the organization. Automatic domain prediction and multi-queue routing are not included in the initial release. The initial experience starts a new thread and does not send prior Assistant conversation history to the live agent.

    0
    jmcginley
    1 month ago
    Kevin Mok
    Kevin MokCommunity Manager

    Minor ML Update: Clearer Outcomes for Tool Calls6. Delivered

    How are we improving the Assistant’s behavior?Failed or empty tool calls now show a clear failure or no-results state, along with guidance on what the user can do next, instead of appearing successful.When is the release date?Frontier: September 9, 2026 Standard: September 14, 2026 Basic: September 17, 2026Technical RestrictionsThis initial release primarily covers Agent Studio Plugins. MCP failure transparency, and more specific action-error messages are not included in this release and are being handled as separate follow-up work.DocumentationDocumentation describing reasoning and tool-failure behavior will be linked here when published.

    0
    Kevin Mok
    1 month ago
    JacekU
    JacekUNew Participant

    Ability to change the Rejection message on an Approval record posted by Moveworks1. New

    For any Service Now approvals, if a rejection is made by the approver a customer facing note is then posted on the Request. It would be good to have the option to improve this message and have the ability to edit it.This would allow for a better clarity for the end user in understanding what has happened with their request and why.

    1
    1 month ago
    Vaishnavi27New Participant

    HR knowledge studio for the HRC cases1. New

    Currently, the Knowledge Studio capability is primarily designed around IT and considers incidents as the source for knowledge creation and management.We would like to have the ability to create a dedicated HR Knowledge Studio that can consider HR Cases (HRCs) from ServiceNow as its source.An HR Knowledge Studio would allow organizations to: Use HR Cases (HRCs) as the primary source for identifying and managing HR knowledge. Keep HR-specific knowledge separate from IT knowledge and incidents. Create a dedicated knowledge experience based on HR case data and recurring HR queries. Improve the ability to identify knowledge gaps and opportunities specifically within HR processes. Provide HR teams with a dedicated space to manage and improve knowledge without impacting the existing IT Knowledge Studio. We explored whether this could be implemented through an agent studio plugin as a workaround. However, a the use case would not provide the same experience and capabilities as a dedicated Knowledge Studio as it hits the LLM limit with a few numbers of articles itself

    0
    1 month ago
    Show more activity

    Filter by product

    • All products
    • Analytics
    • AI Assistant
    • Tool Studio
    • Employee Experience Insights
    • Knowledge Studio
    • Moveworks Setup
    • Enterprise Search
    • Content Integrations
    • Content Gateway
    • Other Integrations
    • Next Gen Triage (2.0)
    • MW4Web
    • Service Management
    • AI Agent Marketplace
    • Agentic Reasoning Engine
    • EmployeeWorks
    • General
    • Channels
    • Assistant Platform
    Terms & ConditionsAccessibility statement