Summarise these selected supplier accounts and assets for our review.
I’ll use the summary fields captured from the selected records and flag context that isn’t included, such as files and related records.
Selected CRM records
Supplier summary
- Account and asset context
- Source record references
- Questions for the record owner
1What’s connected.
Reference selected Salesforce records through @ in Seal: Accounts, Contacts, Opportunities, Leads, Campaigns, Products, Assets and queryable custom objects. Summary fields are shared by default; Include all readable Salesforce fields adds accessible standard and custom fields. The connection only reads records, and files and related-record contents are not included.
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 Salesforce
- Open Settings → Integrations → Set up Salesforce and paste your My Domain home URL.
- Sign in, choose a record type and search its record name.
- Choose Seal groups, keep summary fields unless you intend to share all readable fields, then enable the library. Your account needs API access and read permission for the intended objects and fields.
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 Salesforce. 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.