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
      • Overview
      • FAQ Formatting Guide
      • Troubleshooting Template
      • Q&A Template
DeveloperAcademyCommunityStatus
On this page
  • Sample header 1: How do I format a Question-and-Answer article?
  • Sample header 2: Can there be multiple headers per article?
Knowledge StudioArticle Templates

Template: Question-and-Answer Article

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

Sample header 1: How do I format a Question-and-Answer article?

Break down how-to articles into short, numbered steps like below. Some other best practices:

  1. Each header should deal with a specific task or question.
  2. Try to begin each header with “How do I…” or “How can I…”.
  3. Question-and-Answer articles may include question marks (”?”) in headers, like demonstrated above.
  4. Use actual H1 or H2 formatting for headers, like above.
  5. Avoid additional nested headers.
  6. If possible, limit blocks of text before the numbered steps.

Each header, along with any text below it, will be served as a single snippet in chat.

Sample header 2: Can there be multiple headers per article?

There may be multiple headers per article, each covering a specific task (e.g. one for adjusting calendar views in Outlook, and another for creating a new event).

  1. Sample numbered steps for header 2
  2. Sample numbered steps for header 2

Each of these headers and their text will be served as separate snippets in chat.