# Export Paige documents to Content Central

Paige's native Content Central export: point a scan job at your Content Central server, sign in as a capture user, map each Paige document type to a catalog and document type, choose whether documents file directly or wait in the Coding Queue, and map the fields so they arrive indexed.

Product: paige · Audience: system-administrator · Time: 45 minutes · Last verified: 2026-09-05

Canonical: https://help.ademero.com/paige/integrations/export-paige-documents-to-content-central

**At the end of this guide, every document Paige finishes is captured into Content Central — filed straight into the right catalog and document type with its index fields already filled, or parked in the Coding Queue for a person to finish — exactly as if it had been scanned in with Content Central's own tools, but with Paige's AI having done the reading.**

This is one of Paige's two built-in destinations (the other is Nucleus One). Paige talks to Content Central's own capture services over HTTPS, so there is nothing to install on the Content Central server.

## Before you start: let Paige reach your server

Paige runs in the cloud and connects *in* to your Content Central server. Two things must be true:

1. Content Central's website is reachable from the internet over **HTTPS** at a public address ([Serve Content Central over HTTPS](/content-central/administration/serve-content-central-over-https) if it isn't yet).
2. Your firewall allows inbound connections from Paige's address ranges — they're listed in [Outbound IP ranges for firewall allow-lists](/paige/document-processing/outbound-ip-ranges-for-firewall-allow-lists), which also explains how to test from *outside* your network, the only test that proves anything.

You also need a Content Central account for the export to sign in as. Create one named for the job — "Paige Capture" — and give it capture permission on the target catalog and document types ([Add a user](/content-central/administration/add-a-user)). Documents will show that user as the capturer.

## Step 1 — Connect the scan job to the server

1. In Paige, open **Settings** (the gear at the bottom of the left menu — administrators only), pick the scan job, and choose **Export**.

2. Click the **Content Central** card. The **Content Central Configuration** dialog opens.

3. Enter the **Content Central Server URL** — the address users type to open Content Central, for example `https://contentcentral.example.com`.

4. If your Content Central uses Windows domain (Active Directory) logins, pick the **Domain** from the list; Paige reads the available domains from the server as soon as the URL is valid. Leave it empty for a Content Central-managed account.
   
   **What you should see:** `Retrieved 1 domain successfully.` (or however many you have), or `Connected to server successfully. No domains found.` Either means the URL is right. `Failed to fetch Content Central domains.` means Paige can't reach the server — go back to the firewall section.

5. Enter the **Username** and **Password** of the capture account and click **Test Connection**.
   
   **What you should see:** `Retrieved N catalogs successfully.` If instead you see `Connected to Content Central successfully, but no catalogs were found. Please check your user permissions.`, the login worked but the account has no catalog permissions yet. `Failed to fetch Content Central catalogs. Check your credentials.` is a wrong username or password.

*[Screenshot: The Content Central Configuration dialog with the server URL, domain, and credentials entered and catalogs retrieved]*

## Step 2 — Map each Paige document type

Under **Paige Document Types**, the dialog lists every document type in the scan job. For each one, set three things:

| Setting | What to choose |
| --- | --- |
| **Content Central Catalog** | The catalog the documents belong in |
| **Content Central Document Type** | The document type inside that catalog |
| **Destination** | **Catalog** files the document immediately with the mapped fields. **Coding Queue Personal** parks it in the capture user's own Coding Queue. **Coding Queue Shared** parks it in the shared queue for anyone with access to finish. |

Choose **Catalog** when Paige's extraction is trustworthy for that type and you require human review in Paige. Choose a Coding Queue destination when you want the indexing checked *in Content Central* instead — the fields Paige sends arrive pre-filled in the queue, so the person only confirms.

**What you should see:** `Document type mapping updated: <name>` after each choice, and `Destination updated successfully` when you set the destination.

*[Screenshot: One Paige document type mapped to a Content Central catalog and document type, with Destination set to Catalog]*

## Step 3 — Map the fields

For each mapped document type, each Paige field has a **Select Content Central Field** drop-down listing the fields of the chosen Content Central document type. Map the ones that matter and leave the rest unmapped; unmapped Paige fields are not sent.

Match types: Paige dates to Content Central date fields, amounts to numeric or currency fields, everything else to text. A value that doesn't fit its Content Central field type fails validation on the Content Central side, and the document is rejected for that reason.

**What you should see:** `Content Central Field Mapping Updated!`

*[Screenshot: The field mapping list for one document type, Paige fields on the left and Content Central fields chosen on the right]*

## Step 4 — Connect and turn on auto export

1. Click **Connect** at the bottom of the dialog. **What you should see:** `Connected to Content Central successfully!` and a green **Connected** label on the Content Central card.

2. On the Export page, turn on **Enable Auto Export** and set **Auto Export Settings**: which **Document Types** to send, whether to require **Human Reviewed** = *Reviewed*, and whether to require **Auto Field Entry Complete** = *Yes*. If your destination is **Catalog**, require both. Click **Save**.

Documents already in the scan job aren't sent retroactively. Send those once from the **Documents** page: click **Export**, walk the **Export Documents** dialog (Scope, Filters, Destinations, Confirm), and tick **Content Central** under Destinations.

## Check it worked

1. Process one document through the scan job, review it if required, and wait a minute.
2. In Content Central, open the catalog (or **Work Areas** > **Coding Queue** if that was the destination). **What you should see:** the document, captured by the Paige account, with the mapped fields populated.
3. Open the document and confirm the text is selectable — that's the searchable layer Paige produced.

## When it doesn't work

| Symptom | What it means |
| --- | --- |
| `Failed to fetch Content Central domains.` | Paige can't reach the URL. Check HTTPS, the public address, and the firewall allow-list; test from outside your network. |
| `…no catalogs were found. Please check your user permissions.` | The account signed in but has no catalog permissions. Grant capture rights on the target catalog. |
| `Failed to fetch Content Central document types.` or `…fields.` | The account can see the catalog but not that document type. Check document-type permissions. |
| Document rejected on capture | A mapped value doesn't fit its Content Central field (wrong type, or a required field left unmapped). Fix the mapping or make the field optional. |
| Nothing arrives | Auto export criteria aren't met, or the document was processed before auto export was on. Export once by hand from the **Documents** page. |

Still stuck? Contact Ademero support with the scan job name, the Content Central server URL, the capture account's username (never its password), and the time you expected the document.

## What's next

- [Outbound IP ranges for firewall allow-lists](https://help.ademero.com/paige/document-processing/outbound-ip-ranges-for-firewall-allow-lists)
- [How documents get into Content Central](https://help.ademero.com/content-central/capture/how-documents-get-into-content-central)