> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# PMS knowledge

> Add and override listing knowledge without fighting PMS-synced content.

When a Property Management System is connected, Conduit periodically syncs listing descriptions, amenities, check-in instructions, and reservation context into the workspace. That content appears in Knowledge as source-backed listing content, and the PMS remains its source of truth.

Knowing what the PMS owns is what keeps you from losing edits or creating duplicates.

## Two Kinds Of Listing Knowledge

| Type | Who owns it |
| - | - |
| **PMS-synced content** | Created and updated by the sync. Direct edits can be overwritten on the next run. |
| **Manual pages** | Created by your team in Knowledge. They persist across syncs because they sit outside the PMS-managed source. |

<Info>
  Do not edit PMS-synced content directly. To change what the agent says about a listing, create a manual page with the correction instead.
</Info>

## Add Knowledge For A Listing

<Steps>
  <Step title="Open Knowledge">
    Go to **Agents > Knowledge**, then find or create the folder for the listing or listing group.
  </Step>

  <Step title="Add a page">
    Click the add button and choose **Page**.
  </Step>

  <Step title="Write the content">
    Follow the [Knowledge writing principles](/build-your-agent/what-goes-where/knowledge) and keep the page focused on one topic.
  </Step>

  <Step title="Scope it">
    Apply listing or entity scope so the page only applies where it should. See [Managing Knowledge](/build-your-agent/knowledge-base/managing-knowledge).
  </Step>
</Steps>

## Override PMS Information

If synced data is wrong or incomplete, create a manual page with the corrected information and scope it to the affected listing. The agent retrieves the Knowledge most relevant to the conversation, so the scoped correction takes effect without touching the PMS source.

## Avoid Duplicates

Duplicates appear when PMS-synced content and a manual page cover the same topic, such as two amenity descriptions or two sets of Wi-Fi instructions. They also appear when the same topic exists both globally and at listing level.

To resolve them:

1. Identify which content is PMS-synced and which is manual.
2. Remove manual content that simply repeats the PMS source. Keep the manual page only if it intentionally overrides the source.
3. Where global and listing-level content disagree, keep the scope that matches the real policy.

## Best Practices

* Leave PMS-synced content alone when the PMS is the source of truth.
* Create manual pages for distinct corrections or additions rather than recreating content the PMS already syncs.
* Use clear page titles so manual content does not read like a duplicate of synced content.
* Review listing Knowledge after PMS changes, migration work, or listing updates.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Why did my edit to a listing page disappear?">
    The page was most likely PMS-synced, and the next sync overwrote it. Create a manual page with the correction instead.
  </Accordion>

  <Accordion title="How do I correct wrong PMS data without changing the PMS?">
    Create a manual page with the corrected information and scope it to the affected listing. The agent retrieves the Knowledge most relevant to the conversation.
  </Accordion>

  <Accordion title="I have two versions of the same amenity description. Which do I remove?">
    Remove the manual page if it simply repeats the PMS source. Keep it only if it intentionally overrides the source, and give it a title that makes the override obvious.
  </Accordion>

  <Accordion title="How do I tell whether a page is PMS-synced or manual?">
    Source-backed listing content is managed by the sync and is usually read-only. Anything your team created directly in Knowledge is manual and stays under your control.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.