Read these selected files and prepare a review brief with references.
I’ll use the shared captures where text copying is enabled, and keep each file’s version reference with the brief.
Selected file captures
Source-backed review
- Summary of the supplied evidence
- File and version references
- Gaps to resolve before a decision
1What’s connected.
Select Google Drive files and supported Google document exports for shared @ references in Seal. Keep captured versions linked to their originals and choose whether Neil can read copied text.
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 Google Drive
- Open Settings → Integrations → Set up Google Drive, paste the folder URL and sign in with Google.
- Search and select files directly inside the connected folder.
- Choose Seal groups, review text copying and enable the library. Workspace approval 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.
3Before it goes live.
Access
The organisation library reads only; it makes no changes in Google Drive. 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.