Compare these Benchling entities and summarise the differences in their recorded fields.
I’ll compare the selected entity captures and separate recorded differences from fields that are missing.
Selected custom entities
Entity comparison
- Fields compared across entities
- Differences and missing values
- Entity, schema and registry references
1What’s connected.
Reference selected Benchling Registry entities or Notebook entries from projects the installed app can read. Search Registry entities by name; find a Notebook entry by its exact name or entry ID. Attachments, Results tables, linked-resource contents and sequence data 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 Benchling
- Create and install a dedicated Benchling app and grant it read access to the intended projects.
- Open Settings → Integrations → Set up Benchling, enter the tenant URL and app credentials, then choose Test and connect.
- Choose a project and collection, select Registry entities or Notebook entries and Seal groups, review text copying and enable 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.
3Before it goes live.
Access
The organisation library reads only; it makes no changes in Benchling. 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.