# Link straight to documents and searches (QuickLinks)

URL patterns other systems can build: open a document by ID, land in a folder, run a search with criteria pre-filled, or open a capture page ready to scan — plus the share-this-search links users can copy without knowing any of it.

Product: content-central · Versions: 7.x · Audience: integrator · Time: 15 minute read · Last verified: 2026-09-05

Canonical: https://help.ademero.com/content-central/integrations/link-straight-to-documents-and-searches

**By the end of this page your other systems can link *into* Content Central — this customer's folder, this PO's document, this search already run — with nothing but a URL, and you'll know the two parameter facts that make or break these links.**

All URLs below hang off your Content Central address (shown here as `https://docs.example.com/ContentCentral`). Permissions always apply — a link opens only what its follower is allowed to see — and a signed-out user gets the login page first, then lands on the link's target.

## For users: the copy-a-search button

Before any URL-building: the Search page can hand out links by itself. Run a search and use its share/copy-link control — the copied URL reproduces the whole search (criteria, catalogs, view) for anyone who follows it. For "here's the search, see for yourself" emails, that's the answer; the patterns below are for *systems* that build links.

## Open a document by ID

```
https://docs.example.com/ContentCentral/FolderBrowser/FolderBrowser.aspx?id=<document GUID>
```

The document's GUID is its stable address (visible, among other places, atop its Version History). Store it at capture time — an [XML capture job](/content-central/capture/set-up-an-xml-capture-job) or the API can carry it back to the linking system — and your ERP's "view document" button is this URL.

## Land in a folder

```
.../FolderBrowser/FolderBrowser.aspx?c=Accounts Payable&d1=Bowman Fabrication&d2=PO 8888
```

- `c` — the **catalog name** (URL-encode spaces).
- `d1`, `d2`, `d3`… — one parameter per folder level, matched by name, case-insensitively.

Names, not IDs — which makes these links readable and buildable from data the other system already has (vendor name → vendor folder), at the price that renaming a folder breaks its links.

## Run a search, pre-filled

```
.../Search.aspx?ft=Bowman&execute=1
.../Search.aspx?c=Accounts Payable&dt=Purchase Order&f1=PO&v1=8888&execute=1
```

| Parameter | Meaning |
| --- | --- |
| `ft` | Full-text query |
| `c` | Catalog **name** — repeatable (`c=A&c=B`) |
| `dt` | Document-type **name** — repeatable |
| `f1`/`v1`, `f2`/`v2`… | Field name / value pairs, numbered consecutively |
| `execute=1` | Run it on arrival (omit to just pre-fill the form) |

The second example is the everyday integration: field + value + `execute=1` turns any system's record into a "show me the documents" button.

## Open a capture page, pre-configured

```
.../Capture.aspx?ct=electronic&cm=post&c=Accounts Payable&execute=1
```

- `ct` — capture type: `electronic`, `directscan`, `directscanzonal`, `qcard`, `qcardpacket`, `form`
- `cm` — coding method: `pre`, `post`, `versatile`, `ocronly`
- `dq` — queue destination for `versatile`: `personal` or `shared`
- `fpc` — fixed page count; `eod=1` — include the end-of-document QCard
- `c` — catalog name; `execute=1` — go immediately

The intranet's "scan an invoice" link opens the right capture page with the right choices already made.

## The two facts that make or break links

1. **Legacy parameters take names; the copied search links carry IDs.** Build with `c=`/`dt=`/`f1=` and you're in the name world — stable until something is renamed. The user-copied links are opaque by design; don't try to hand-construct those.
2. **There's nothing to enable and nothing to secure separately.** QuickLinks are always on, and they confer no access — resolution happens under the follower's own permissions. A link to a document someone can't see behaves as if the document doesn't exist.

**Success check:** build the field-search URL for a value you know exists, open it in a private window — login page, sign in, results already on screen. That round trip is every integration's demo.

## What's next

- [Connect another system to Content Central](https://help.ademero.com/content-central/integrations/connect-another-system-to-content-central)
- [Set up an XML capture job](https://help.ademero.com/content-central/capture/set-up-an-xml-capture-job)