How source connections work

A connection grants Sentium read access to a bounded provider scope. It does not make Google Drive, Box, or GitHub the controlled system of record for work performed in Sentium.

The connection boundary#

1. An authorized user approves access through the provider or follows an approved guided connection flow.
2. The user selects the folders or repositories that Sentium may read.
3. Sentium maps that selection to the correct tenant and company or device scope.
4. Each accepted file becomes an immutable version in the Source Inbox.
5. Sentium scans and processes that version before it becomes available for retrieval, citation, review, or drafting.

Provider content becomes a versioned Sentium snapshot. Historical citations remain pinned to the exact source version used during review. The Agent and drafting workflows never live-read provider files; they retrieve only processed, tenant-authorized Sentium versions.

Roles remain separate#

• Provider administrators control whether an application may be authorized in their environment.
• Sentium workspace administrators control which Sentium users and devices can use connected sources.
• Source owners choose the folders or repositories they are permitted to share.
• Reviewers decide whether extracted or inferred material can support regulated work.

Authorization alone never promotes source material into controlled evidence. Review and approval remain explicit. See the source data lifecycle for the complete sequence.