What Integrations shows

Integrations is where you see how your tools connect and how data reaches Pytheus. Most of it is a read-only record: observed counts and timestamps describing what has already happened, rather than projections.

What it is, and is not

Integrations records the relationships your team documents and the ingestion Pytheus has performed. For most of the surface, a tool link marked connected reflects what has been recorded about that link rather than a live health check.

Contract sources are the exception, and the difference matters. Where you have connected a contract source, Pytheus signs in with the access you granted and re-checks it on a schedule, so new agreements appear without anyone uploading them. Those entries describe a live connection; the rest of the surface does not.

What it tracks

Each tile drills into detail:

• Connected tool links: the tool-to-tool relationships your team records. See Tool links.

• Contract sources: connected document sources that Pytheus re-checks on a schedule for new agreements.

• Evidence sessions: the intake sessions that turn documents into structured proof. See Evidence and documents.

• Data imports: the import jobs that seed tools, contracts and assessments. See Data imports.

• Contract documents: the documents attached to your contracts.

Outside contract sources, read Integrations as a record of what has happened rather than a promise of what is happening now.

Start with Tool links to see how your stack is wired together.