> For the complete documentation index, see [llms.txt](https://docs.prove.ly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prove.ly/getting-started/connect-your-sources.md).

# Connect your sources

`GETTING STARTED`

Provely sits adjacent to your stack, not competing with it. Two kinds of sources power everything:

#### Identity sources

Your IdP or HR system tells Provely *who* exists, their role, and their team — so new hires are qualified on day one and role changes trigger requalification on their own.

#### Policy sources

Your policy repository tells Provely *what* people must understand, and which version is current. When a policy changes, the affected population is flagged automatically.

{% hint style="info" %}
Start small: one team and one policy is enough to see your first coverage gaps. Expand at your own pace — manual to automated, no big-bang rollout.
{% endhint %}

***

#### What Provely tracks once connected

✓ Who is in scope for each policy

✓ Which policy version each verification was made against

✓ Population changes — joiners, movers, leavers

✓ Coverage gaps opening on high-risk teams


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prove.ly/getting-started/connect-your-sources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.