Company and device source scope

Every selected folder, repository, or uploaded file is mapped to an explicit Sentium scope. Set that scope before processing so the material is never discoverable more broadly than intended.

Company-wide sources#

Company sources can support multiple devices inside the same tenant according to workspace policy. Appropriate examples include organization-level quality procedures, shared templates, approved terminology, and cross-product policies.

Company-wide does not mean public and does not mean cross-tenant. Tenant isolation and role-based access continue to apply.

Device-specific sources#

Device sources remain scoped to one device. Appropriate examples include design inputs, verification protocols, risk files, device-specific software documentation, and submission evidence.

Use device scope whenever the material should not appear in retrieval or drafting for another device.

Changing a mapping#

An authorized user may change a source mapping when the business context changes. Sentium audits the change and applies the new scope prospectively. Changing a mapping does not rewrite historical citations, approvals, or the source version that supported an earlier decision.

Use sync and freshness to understand what happens when content changes inside a selected scope.