> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inploi.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Feature integration requirements
> Which ATS integration models each inploi feature needs before it can be switched on.
The [capability matrix](/integrations/ats/capability-matrix) answers "what does ATS X support?". This page answers the other half: **"what does feature Y need?"**. Read the two together to work out which inploi features a customer can run on their ATS — for example, "with an ATS that only supports Job import, you can run job search, job alerts, the candidate agent, and organic distribution, but not application submission or dynamic flows."
This is internal-facing reference material for discovery, scoping, and support triage. It is a **first-pass mapping** and should be confirmed against the [capability matrix](/integrations/ats/capability-matrix) and the `api` integration library before relying on it. Where a requirement is unconfirmed, it is flagged in the notes column rather than assumed.
## Requirements by feature
Each feature is mapped to the [four integration models](/integrations/ats/ats-integrations#the-four-integration-models) it depends on. **Required** means the feature cannot function without that model; **—** means it is not needed.
| Module | Feature | Job import | Submitting applications | Workflow sync | Disposition | Prerequisites and notes |
| ---------------- | ------------------------ | :--------: | :---------------------: | :-----------: | :---------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CMS | Search and job pages | Required | — | — | — | Jobs populate the search plugin. The richer the job data from the ATS, the more filtering options are available. |
| CMS | Job alerts | Required | — | — | — | Optional part of the search plugin. inploi must be the **data controller** (not just processor), because it stores candidate PII. |
| Insights | Analytics | Required | Required | — | Required¹ | ¹ Timestamped status updates (disposition) are critical to reconcile ATS outcomes to inploi analytics. |
| Flows | Static flows | Required | Required | — | — | inploi does **not** ingest ATS workflows. Needs jobs (to match the flow to a job) and application submission (to post into the ATS). |
| Flows | Dynamic flows | Required | Required | Required² | — | ² inploi retrieves the workflow from the ATS and treats it as a single flow. |
| Agents | Candidate agent | Required | — | — | — | Reads the job index; does not submit or update applications. |
| Agents | Scoring agent | Required | Required³ | — | — | ³ Also needs **application write-back** to push score/status into the ATS (the update side of Submitting applications). Confirm the ATS accepts extra fields for score and rationale — write-back is currently only available on a subset of integrations. |
| Agents | Interview agent | — | — | — | — | ATS capability requirements not yet confirmed. |
| Job Distribution | Organic job distribution | Required | — | — | — | Requires inploi-managed job pages in order to distribute jobs externally. |
## How to read a row
* **Job import only** is the minimum for a careers site: search, job pages, job alerts, the candidate agent, and organic distribution all work as soon as vacancies are flowing in.
* **Submitting applications** unlocks the apply-through-inploi features: static flows, and (as an input) analytics and the scoring agent.
* **Workflow sync** is what separates **dynamic flows** (workflow read from the ATS) from **static flows** (built in inploi).
* **Disposition** is what makes analytics reflect real downstream outcomes rather than just applications submitted.
## Related pages
What each ATS supports across the four integration models.
Transport model and partner API documentation per ATS.