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
  • Getting Started
    • Welcome to Moveworks
    • Roadmap & Release Notes
    • Moveworks Best Practices
    • Labs
    • Professional Services
    • Support
  • AI Assistant
    • AI Assistant Overview
    • Capabilities
      • AI Disclaimers
      • Configure Disclaimers & Labels
      • Approvals Queue
      • Channel Resolver
      • Code Interpreter
      • Display Configurations
      • Domains
      • Email Composer
      • Employee Communications
      • Notifications Settings
      • People & Places Lookups
      • Self Knowledge
      • Smart Handoff
      • Text Translator
      • Personalized Responses
      • World Knowledge App
    • Web Experiences
    • Analytics & Performance
  • Enterprise Search
    • Overview
    • Agentic RAG Overview
    • Content Ingestion Platform
    • Profile Boosting
    • Retrieval
    • Permissions Platform
    • Built-in Content Connectors
    • Build your own Content Connectors
    • Configure Search
    • Configure Enterprise Search
    • Vetted Content
    • Writing AI-Ready KB Articles
    • Document Chunking and Snippetization Overview
  • Productivity Boost
    • Overview
    • Configure Productivity Boost
    • Quick GPT
    • Calendar Management
    • Brief Me
DeveloperAcademyCommunityStatus
On this page
  • Overview
  • How does it work?
  • How to Configure it?
AI AssistantCapabilities

Personalized Responses

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

World Knowledge App

Next
Built with

Personalized Responses requires that the AI Assistant Reasoner is at GPT-5; GPT-4.1 is not supported.

Overview

Personalized Responses tailors answers from the AI Assistant to each employee—improving relevance, clarity, and trust - based on the content (Files, KBAs, etc) retrieved. By bringing key user attributes, including any custom attributes, into working memory, the AI Assistant can provide a more tailored response.

Limitations

  • Only impacts the Knowledge Search / Enterprise Search Plugin within the AI Assistant
  • Personalization uses attributes to tailor the response it gets from knowledge and file search
  • Resource queries can be rewritten using information from personalization attributes

How does it work?

By default, the Moveworks AI Assistant will leverage some of the native attributes that are already part of the identity integration to create a Personalized Response:

  • Location
  • Country code
  • Role
  • Department

In addition, admins can configure custom attributes to also be leveraged as part of Personalized Responses. Here are example categories of custom attributes that can be helpful.

Category

Examples

Primary Use Case in Search

Organizational & Role

-Job Grade
-Business Unit
-Employee Level

Content relevance (e.g., sales vs. engineering topics) within the retrieved body of text

Employment & Status

-Salary Basis Code
-Years of Service
-Employment Type (Full-time, Intern, Contingent)

Specific answers for HR, payroll, and benefits (e.g., “Your specific vacation accrual is…”) if written within the retrieved body of text

Geo Location

-Subsidiary
-Building
-Work location (Office or Remote)

Location-specific info (e.g., local holidays, office facilities, regional policies) if written within the retrieved body of text

Device Profile

-Laptop OS (Mac or Windows)
-MDM Status (Enrolled vs Not Enrolled)

Targeted IT support and accurate “how-to” guides (e.g., “Here is the VPN guide for macOS…”) if written within the retrieved body of text

The combination of both native and custom attributes are injected to the system prompt, which is part of the working memory. When the AI Assistant provides a summary, based on retrieved content, it will tailor the response with these attributes.

How to Configure it?

  1. Ensure that the desired native and custom user attributes are mapped into the user proto (In Moveworks Setup > User Identity > Import Users )

    Ensure user attributes are mapped to the user proto will be automatically used for personalization, as part of GPT-5. See /agent-studio/core-platform/user-identity/user-attribute-reference#/ for full list of attributes that should be mapped. If the admin would like to leverage location or any general attribute from a non-primary source, they will have to do an override the native attribute.

    Additionally, custom attributes can be ingested via Content Gateway. See /users within the API Spec.

  2. Map the desired user attribute keys to friendly names and descriptive labels that will be provided to the Assistant (In Moveworks Setup > AI Assistant > Advanced Setting > User Attribute Personalization)

    Identify a subset of attributes that will be most beneficial for personalization


  3. To confirm the attributes have been ingested, visit Moveworks Setup > Core Platform > Imported Users to validate that the attribute has been ingested in the “All Users” view.