# Manage a Confluence or Pylon knowledge base

import { Aside, Steps, Tabs, TabItem } from '@astrojs/starlight/components';

<Aside type="note" title="Request access">
  Knowledge base management is available on request. Contact support@ekline.io with your organization name to enable it for Confluence or Pylon.
</Aside>

Docs Agent helps internal teams keep a knowledge base accurate and up to date. Connect an internal Confluence space — for example, an engineering or support team's knowledge base — or a Pylon knowledge base used by your support team. The agent updates individual pages, maintains an entire space, and improves articles from sources like support tickets, then publishes the changes straight back to the source with no copying between tools.

This guide starts with a single page, then shows how the same workflow scales to the whole knowledge base. By the end, your edits are live in Confluence or Pylon.

<Aside type="note" title="Managing a knowledge base vs. referencing one">
This guide covers a two-way workflow: the agent reads a page **and writes your changes back**. To pull content from a page into new documentation without editing it in place, see [Integrations](/agent/integrations/) instead.
</Aside>

## Before you begin

You need:

- An EkLine account with Docs Agent and knowledge base management enabled.
- A connected Confluence or Pylon knowledge base with at least one space or knowledge base marked as managed (see [Connect your knowledge base](#connect-your-knowledge-base)).
- Permission to edit the page or article you want to update.

## Connect your knowledge base

An organization administrator connects the knowledge base once. The agent can then read from and write to the spaces or knowledge bases you select.

<Tabs>
  <TabItem label="Confluence">
    <Steps>
    1. Connect Confluence under **Settings > Organization > Integrations**.
    2. Go to **Settings > Organization > KB Management**.
    3. Enable **Manage Confluence**.
    4. Select each Confluence space you want the agent to manage.
    5. Click **Save**.
    </Steps>

    The agent can now read and update pages in the selected spaces.
  </TabItem>
  <TabItem label="Pylon">
    <Steps>
    1. Go to **Settings > Organization > KB Management**.
    2. Enable **Manage Pylon**.
    3. Paste your **Pylon API token** and click **Connect**.
    4. Select each Pylon knowledge base you want the agent to manage.
    5. Set a **Default author**. New articles the agent creates are attributed to this Pylon user.
    6. Click **Save**.
    </Steps>

    The agent can now read, update, and create articles in the selected knowledge bases.
  </TabItem>
</Tabs>

<Aside type="note" title="Access follows your permissions">
The agent can only read and update content the connected account has permission to change. Only the spaces and knowledge bases you mark as managed are available to the agent.
</Aside>

## Step 1: Open the editor

<Steps>
1. Log in to your [EkLine dashboard](https://ekline.io/dashboard).
2. Click **Docs Agent** in the left navigation.
</Steps>

## Step 2: Retrieve the page

Ask the agent to fetch the page you want to update. The agent loads it into the editor panel as Markdown you can edit.

<Tabs>
  <TabItem label="Confluence">
    Paste the page URL:

    ```
    Retrieve this Confluence page and fix the outdated CLI flags
    in the installation section:
    https://your-org.atlassian.net/wiki/spaces/ENG/pages/123456
    ```
  </TabItem>
  <TabItem label="Pylon">
    Name the article, or list the knowledge base first:

    ```
    List the articles in our Pylon knowledge base, then retrieve
    the "Resetting your password" article so I can update it.
    ```
  </TabItem>
</Tabs>

The agent reads the live page and writes it into the editor panel, keeping the formatting the source needs for a clean round-trip.

## Step 3: Review the retrieved content

Read through the page in the editor and confirm it matches what you expect to see in the knowledge base. Editing a page you retrieved keeps your changes scoped to that page.

## Step 4: Edit with follow-up prompts

Refine the page by continuing the conversation. The agent keeps the context from your first prompt, so you can build on the content incrementally. You can also edit directly in the editor panel.

<Tabs>
  <TabItem label="Update a section">
    ```
    Rewrite the "Requirements" section to list the new minimum
    version, and add a note about the deprecated config option.
    ```
  </TabItem>
  <TabItem label="Improve clarity">
    ```
    Tighten the troubleshooting steps into a numbered list and
    remove the duplicated paragraph about cache clearing.
    ```
  </TabItem>
  <TabItem label="Add from a source">
    ```
    Add a new FAQ entry based on this Slack thread:
    https://workspace.slack.com/archives/C01234/p1234567890
    ```
  </TabItem>
</Tabs>

## Step 5: Publish your changes

When the page is ready, publish it back to the source.

<Steps>
1. Enable **View All Changes** in the toolbar to review a diff of your edits.
2. Make any final adjustments in the editor panel.
3. Click **Update KB** to publish. The tooltip reads **Publish your knowledge base edits**.
</Steps>

The **Update KB** button replaces **Raise PR** when you work on a knowledge base, because there is no pull request to open — your approval publishes the edits to the source instead.

<Aside type="caution">
Publishing overwrites the live page immediately. Your edited content replaces Confluence pages, and Pylon articles update in place. Review the diff before you publish. For Pylon, publishing does not change whether an article is listed as published or unpublished.
</Aside>

## Verify the update

Confirm the change reached the source:

- **Open the live page.** The Confluence page or Pylon article shows your edits.
- **Check the structure.** Headings, tables, and links render the way they did before, with your changes applied.
- **Confirm the diff matched.** What you reviewed under **View All Changes** is what appears on the live page.

## Maintain the whole knowledge base

The same workflow scales beyond a single page. Point the agent at a managed space or knowledge base, and it can review many pages at once, apply consistent updates, and create new articles — publishing each change back with **Update KB**.

<Tabs>
  <TabItem label="Audit a space">
    ```
    Review the Engineering space for pages that still reference the
    old deployment command. Update each one to the new command and
    summarize what you changed.
    ```
  </TabItem>
  <TabItem label="Improve from support tickets">
    ```
    Our support team keeps answering the same question about SSO
    setup. Draft a new help center article that covers it, based on
    this thread: https://workspace.slack.com/archives/C01234/p1234567890
    ```
  </TabItem>
  <TabItem label="Keep articles current">
    ```
    Compare the "Billing FAQ" article against the latest pricing
    page and update any answers that are out of date.
    ```
  </TabItem>
</Tabs>

Review each change under **View All Changes** before you publish. For new Pylon articles, the agent uses the default author you set in **KB Management**.

<Aside type="tip" title="Pull in more context">
Combine knowledge base management with [Integrations](/agent/integrations/) to improve articles from real usage — reference Slack support threads, Jira or Linear tickets, or product analytics in the same prompt.
</Aside>

## Troubleshooting

| Problem | Cause | Fix |
|---------|-------|-----|
| The space or knowledge base isn't available to the agent | It isn't marked as managed, or the integration isn't connected | Enable it under **Settings > Organization > KB Management** and confirm you selected the space or knowledge base |
| The agent can't retrieve a page | The connected account lacks permission, or the URL is wrong | Verify you can open the page yourself, then paste the exact page URL |
| The **Update KB** button is disabled | There are no changes to publish | Make an edit first — the button enables once the page differs from the retrieved version |
| A new Pylon article can't be created | No default author is set | Set a **Default author** under **Settings > Organization > KB Management** |

## Next steps

- [Update and review](/agent/update-review/) — Keep documentation in sync with code changes.
- [Integrations](/agent/integrations/) — Reference Slack, Notion, Linear, and more in your prompts.
- [Customize for your organization](/agent/custom-instructions/) — Match your knowledge base's tone and structure with custom instructions.