Using entities in Benchling’s Registry as treatments within Benchling In Vivo

  • Updated

Leverage the Benchling In Vivo-Benchling integration to track the complete R&D lifecycle of an upstream therapeutic.


Companies using Benchling to manage upstream therapeutic development and subsequently using Benchling In Vivo to manage in vivo work can now directly utilize registered therapeutics as Treatments within Benching In Vivo via the Benchling integration. Note: If you do not have the Benchling In Vivo-Benchling integration for your organization and would be interested to learn more, please contact your Benchling point of contact or reach out via


An upstream therapeutic such as a drug candidate, cell line, virus, antibody etc. is developed and validated before being administered to animals for pre-clinical in vivo testing. To evaluate the toxicity and efficacy of this test agent, tissue samples are often collected from the animals which, along with other data collected during the study, need to be traced back to this therapeutic to inform downstream processing and data analysis. This treatment feature in the Benchling In Vivo-Benchling Integration allows companies using Benchling and Benchling In Vivo to connect their upstream R&D work to downstream in vivo studies, bioanalytical work, and beyond. This is primarily managed through entity links in the Benchling registry which ensures accurate data connection, ultimately allowing for seamless collaboration and an end-to-end data trail for their research.



The treatment syncing feature includes:

  • The ability to query the Benchling Registry for an upstream therapeutic directly within Benching In Vivo when creating a treatment in the Benching In Vivo platform.

  • User-friendly search and select allows for selecting treatments from either the Glossary or the Benchling Registry, making it simple to find the appropriate therapeutic for the treatment.

  • Quick links back to Benchling from In Vivo to the selected Treatment entity are available when a registered Benchling entity is used as a Treatment.

  • Direct URL links from the Treatment entities created in Benchling by the integration to the corresponding items in Benching In Vivo.

  • Each treatment created in studies generates a new treatment entity in Benchling with an entity link to the selected upstream therapeutic if a Benchling registered custom entity has been selected.

    • This treatment entity holds additional information such as dose, stock and volume details as well as any mapped custom metadata that was entered in Benching In Vivo.

  • When a treatment is assigned to a Group in Benching In Vivo, an entity link will be created on the Group entity in Benching, associating the Group with the relevant Treatment entity.



  • Only registered custom entities can be used as Treatments in Benching In Vivo.

  • Each new treatment created in Benching In Vivo will generate a new Treatment entity in Benchling regardless of if this treatment has been used before in another Study.

  • All custom entities accessible to the Benchling In Vivo Integration in Benchling are viewable by any end user in the platform.


To view a demo video of this feature in the integration, see the link here.



This help article provides a simple guide on how to use this feature to sync treatments between Benchling and Benching In Vivo. By following these steps, you can seamlessly connect your upstream R&D work in Benchling with in vivo testing in Benchling In Vivo, and to further downstream work in Benchling.


Jump to:


Treatment Creation

  1. In Benchling In Vivo, navigate to the Treatment subtab of the Treatment Groups page within a Study

  2. Create a new treatment by clicking “add new”.

  3. You now have the option to either select a treatment from the studies glossary or an upstream therapeutic from your connected Benchling Registry as the treatment name.

  4. To use an entity from Benchling, utilize the field as a search input to browse upstream therapeutics. Benching In Vivo should return matches within ~15 seconds.

    • The Treatment name dropdown will display treatments that are in the Glossary, you will not automatically see available Benchling entities until you start typing into this field.

    • Tip: For easiest navigation, use the Registry ID of the exact entity you would like to use as a treatment. This will prevent multiple matching results from appearing, as every Registry ID is unique.

  5. Add treatment information including dose details and metadata and click “Save”.

  6. All treatments using a Benchling registered entity will display the Benchling logo to the right. This is a clickable, direct link to the entity in Benchling which you can use to verify the selection if desired.


Registering the Study Treatment

  1. When you create a treatment in Benching In Vivo, the integration will automatically register a new Treatment entity in Benchling with information such as dose, stock details and other metadata.

  2. If you have selected a registered entity from Benchling as the treatment, the integration-made Treatment entity will have a direct entity link to the corresponding therapeutic entity.

  3. If you used a treatment option from the Glossary, the integration-made Treatment entity will not have a link to an upstream therapeutic but will include the name of the treatment from the Glossary.


Group Association

  1. Assign the treatment to a group in Benchling In Vivo.

  2. The integration will create an entity link on the corresponding group entity, connecting it to the newly registered treatment.

  3. Click on the Benchling logo beside the treatment name in the Treatment groups page to open the treatment in a new Benchling tab.



If no results are displayed after 15 seconds, this is most likely due to one of the following:

  • The entity-syncing feature in the Benchling In Vivo-Benchling integration has not yet been enabled for your organization

  • The Benchling In Vivo-Benchling integration does not have permission to use the entity you are searching for.

  • The entity you are searching for is not registered.

  • The entity you are searching for is not a custom entity.

  • There is a typo in your search.


Was this article helpful?

Have more questions? Submit a request