How to connect a source

Open Setup › Connections

In the rail choose Setup, then Connections in the panel (/p/<slug>/setup/connections). The page lists the program’s connections with provider, status, health, enabled flag, write policy, pinned API version and last sync. The header summarises the providers and their release status. Needs program.connections.read.

Add a connection

Choose Add connection (needs program.connections.manage). In the form that expands in the connections list pick a Provider from literature_search (“Literature search”), benchling (“ELN connector”), veeva_qualitydocs (“QMS/SOP connector”), document_library (“Document library”) or analysis_tools (“Analytical and design tools”), give it a Name, optionally pick a Stage (the program’s current stage is the default) and submit. The form calls POST /programs/{program_id}/connections; the record appears with status pending until the credentials are configured (platform keys for the literature sources; per-connection service credentials for the two read-only connectors). Secret values are never stored in the database: secret_refs hold references only. Connections are program-scoped and carry scope_rules, write_policy and api_version.

Trigger a sync run

Select the connection, then Sync now (needs program.connections.sync). This calls POST /programs/{program_id}/connections/{connection_id}/sync and queues a sync run with trigger manual. The run list under the connection (GET .../connections/{connection_id}/runs) shows it move from queued to succeeded (or skipped for a provider without an adapter) once the worker’s background lane claims it.

Register a source by hand

In the rail choose Evidence, then Sources in the panel (/p/<slug>/evidence/sources). Choose Add source (needs evidence.sources.manage), pick a Kind (publication, eln_entry, protocol, report, dataset, sop_document, registry_record, preprint or other), enter a Title, optionally a Citation, an External reference (a DOI, PMID or record id in the connected system), a Licence code and a Summary, and submit. The source is created with status pending, origin = human and a “Saved” confirmation. Sources the agent proposes in the console arrive the same way with origin = agent after you approve them.

Link the source to a question

Open the source and link it to a question, finding or hypothesis (needs evidence.sources.link, route POST /programs/{program_id}/evidence/sources/{source_id}/links with target_type in question, finding or hypothesis). Findings that cite the source keep the link in source_ids.