Integration guideOrganisation library

Microsoft Outlook

Reference selected emails from your Microsoft 365 mailbox in documents, comments and Neil.

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

Create a timeline from these selected emails and list the unanswered questions.

Neil

I’ll use the shared message bodies and headers. Attachments and other mailbox messages aren’t included.

Selected email captures

What you get

Correspondence timeline

  • Events in date order
  • Message references for each event
  • Outstanding questions and follow-up
Illustrative work with Microsoft Outlook: a request to Neil, the source it reads and what it returns.

1What’s connected.

Reference selected emails from your Microsoft 365 mailbox in documents, comments and Neil. Optional copying includes the message body and basic headers. Attachments and shared mailboxes are excluded.

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 Outlook

  1. Open Settings → Integrations → Set up Outlook and sign in with your Microsoft 365 work account.
  2. Choose a top-level mail folder, search by subject and select sent or received messages.
  3. Choose Seal groups and review the message text you will share before enabling the library.

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 Outlook. 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 →