Integration guideOrganisation library

Microsoft SharePoint

Share selected versioned SharePoint files through @.

Illustration of a seal beside a benchtop bioreactor and a laptop displaying culture trends.

Read these selected files and prepare a review brief with references.

Neil

I’ll use the shared captures where text copying is enabled, and keep each file’s version reference with the brief.

Selected file captures

What you get

Source-backed review

  • Summary of the supplied evidence
  • File and version references
  • Gaps to resolve before a decision
Illustrative work with Microsoft SharePoint: a request to Neil, the source it reads and what it returns.

1What’s connected.

Share selected versioned files from a SharePoint site with chosen Seal groups. Use @ references in documents, comments and Neil; optional text copying supports readable files. Opening the original uses each reader’s SharePoint permissions.

Connection setup and permissions

An organisation admin connects the source, selects records and chooses the Seal groups that can read their captures. Sharing starts after review and a successful sync. Use @ in documents, comments and Neil. Disabling sharing blocks new reads; turning text copying off removes stored text; disconnecting deletes the copies. Original links use the reader’s source-system permissions.

Set up Microsoft SharePoint

  1. Open Settings → Integrations → Set up SharePoint and enter the site URL.
  2. Sign in with Microsoft, choose a document library and select files with version history enabled.
  3. Choose Seal groups, review text copying and enable the library. Microsoft administrator consent may be required.

2Connect in Seal.

Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.

Open Seal

3Before it goes live.

Access

The organisation library reads only; it makes no changes in Microsoft SharePoint. Define which records are shared and which Seal groups can read them.

Data and failure handling

Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.

Verification and release

Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.

Read the assurance detail →