Benchling provides a robust platform for managing scientific data and workflows. Proper configuration of your tenant ensures that your organization can effectively collaborate, maintain data integrity, and streamline research processes. A well-configured tenant is crucial for enforcing data integrity, scaling operations, and unlocking powerful reporting capabilities across the Benchling platform. This guide walks you through the essential steps to set up your Benchling tenant, from user management to schema configuration and permissions.

Manage organizations, teams, and users

Organization, team, and user management is the foundation of configuring your Benchling tenant. This structure determines how data is shared, how permissions are inherited, and how collaborators interact across your tenant.

Create a new Organization

Tenant Admins can create new organizations in Benchling when onboarding a new group or setting up a new business unit. Through this process, you can share specific projects and assign initial members or teams:

1. In the bottom-left corner, click your avatar icon, then click Create or join organization
2. Click Create an organization
   
   
    
3. Fill out the following fields:
   • Give your organization a name
   • Give your organization a handle (no spaces) (a unique identifier other users can search for)
   • If desired, upload a file to use as the organization avatar
4. If desired, invite members or teams to join the organization. Invited users receive an email prompting them to join, or they can be added manually after creation via the Members tab in the Organization Settings
5. Click Next: Share Projects
   
6. If desired, choose projects to share with the organization. You can set permissions using the Permissions dropdown options.
7. Click Share and Complete Setup

Alternatively, you can create an organization from the Organizations tab in the Tenant Admin Console by clicking Create organization. If you choose this method, you can set up the organization name and handle and add members/projects after the organization has been created.

Create teams

Teams simplify user management by enabling permission assignment at a group level. Tenant Admins and User Admins can create teams from the Tenant Admin Console:

1. In the bottom-left corner, click your avatar icon, then click Tenant Admin Console
2. Click the Settings tab, then select Data Modifications
3. Click the Teams tab
4. Click Create team
   
5. To add members to the team, click on the Members tab in the Team Settings, search for the user you want to add in the search box at the top right, then click Add Member
6. Set the member’s role as either Admin or Member:
   • Admin – Can manage team settings and often receive elevated access when the team is assigned as a collaborator
   • Member – Standard access; receives the team's default project permissions
     Note: We recommend assigning Admins to team leads and program managers, and Members to everyone else

If you have Organization Administrator permissions, navigate to the Teams tab of your Organization and click Create team to create a team.

Create users

Before users can contribute to projects or access data, they must be added to the tenant and assigned to the appropriate organization and team by the tenant admin. This can be done individually, as described below, or in bulk. 

If your organization uses SAML single sign-on, your tenant may be configured to enable users to create a user account when they first access Benchling through SAML SSO. This configuration enables you to control user access using a Benchling Active Directory group. 

To check whether user signups are enabled on your tenant:

1. In the bottom-left corner, click your avatar icon, then click Tenant Admin Console
2. Click the Settings tab
3. Select Configurations from the left menu
4. Scroll down to the Security section, then check whether Signups is listed as Enabled or Disabled
5. To change this setting, contact Benchling Support

If your organization is not configured to allow user signups, then user accounts must be provisioned by a user with Tenant Admin or User Admin permissions.

To provision users to your Benchling tenant:

1. Go to the Users tab of the tenant admin console
2. Click Create Users
3. Use the textboxes to add the user’s name, email, and username
4. Use the + icon to add additional users
5. If you would like to associate the user with an organization, optionally use the organizations dropdown to designate which organization they should join and use the role dropdown to assign them admin permissions if needed
6. If you would like to associate the user with a team, optionally use the teams dropdown to designate which team they should join and use the role dropdown to assign them admin permissions if needed
7. Once you have created all the users and associated them with any organizations and teams, click Create 

To bulk create users, click Upload spreadsheet where you can copy over user information in CSV format to go through the creation flow. 

Note: if you use an SSO to log-in, make sure to match usernames and emails to the SSO system. 

Suspend users

Suspending users is important for managing active access, especially when team members leave or change roles. Rather than deleting accounts, you can deactivate (or suspend) users while preserving their ownership and activity history. Suspended users cannot log in or access data, but their content remains accessible to collaborators.

To suspend a user while keeping their data associations:

1. In the bottom-left corner, click your avatar icon, then click Tenant Admin Console
2. Click the Users tab
3. Search for the user(s) you want to suspend
4. To suspend an individual user, click the … icon in the user row, then select Suspend user. Alternatively, to suspend users in bulk, click the checkbox next to each user’s name that appears when you hover over the row, then click the … icon in the page header, then select Suspend users
5. To unsuspend users, follow the same steps, then select Unsuspend user(s)

Configure the Unit Dictionary

The Unit Dictionary in Benchling enables you to define standardized units that can be applied to schema fields. It ensures consistent data entry, enables unit-aware fields, and enables automatic unit conversions across your tenant. By establishing a set of supported units for each measurement type, your team can avoid data inconsistencies and streamline downstream calculations.

Each unit in Benchling is organized under a unit type (e.g., Volume, Mass, Time). Unit types act as categories for related units and must be defined before you can assign any units to a field. Once a unit type is created, you can specify the accepted units within it (e.g., liters and milliliters for Volume). These units are then referenced when configuring fields in a schema.

Some unit types and units come pre-configured in your Benchling tenant. However, you may need to create new unit types or expand existing ones to reflect your organization’s specific measurements.

Tenant admin permissions are required to add unit types or units to the Unit Dictionary.

Add default unit types

Benchling includes several pre-configured unit types and units that are commonly used across scientific workflows. A subset of these pre-configured unit types and units are automatically added to the Unit Dictionary on every tenant. These include:

Benchling includes several pre-configured unit types and units that are commonly used across scientific workflows. A subset of these pre-configured unit types and units are automatically added to the Unit Dictionary on every tenant. These include:

To add additional preconfigured unit types and/or units to your Unit Dictionary:

1. In the bottom-left corner, click your avatar icon, then hover over Feature Settings, then click Unit dictionary
2. To add a new pre-configured unit type or unit, click Add unit type
3. On either the SI units or PD units tab, click on the desired unit type
4. Select the checkboxes for the units that you want to add to your unit dictionary; if you only want to add the base unit (which is selected by default), click Add to dictionary
   • Note: the Save button will appear greyed out, this is normal
5. Click the < icon to navigate back to the previous page, where you can add additional units as desired
6. Click Save to add the units and/or unit types to your Unit Dictionary
7. For each Unit type, expand the Inventory-specific settings to select whether the units in each unit type should be included as options in the container quantity and/or concentration fields on inventory schemas

Add custom unit types or units

If you have custom unit types or units that are not included in Benchling by default, you can create new unit types or units in your tenant. We strongly recommend verifying that your desired unit type/unit is not available on the pre-configured list before creating your own. To create custom unit types:

1. In the bottom-left corner, click your avatar icon, then hover over Feature Settings, then click Unit dictionary
2. Click Add unit type
3. To add a custom unit type, click on the Custom tab
4. Enter a name for the unit type
5. Set the Base unit name and Base unit symbol for your unit type (e.g. for mass, the base unit name is kilogram and the base unit symbol is kg)
6. If your custom unit type can be defined in terms of other existing units in your dictionary (e.g. concentration = “amount of substance”/”volume”), set the formula in the formula editor. Alternatively, if your unit type is a dimensionless quantity (e.g. “plane angle” or “cell count”), leave the formula blank
   Note: To select the operator, hover over the area next to the first unit
   
   
7. Click Add unit type to add to your Unit Dictionary

To create custom units within either a default or custom unit type:

1. In the bottom-left corner, click your avatar icon, then hover over Feature Settings, then click Unit dictionary
2. In the desired unit type, click the + button next the Units header to add an additional unit
3. Set the Unit name, Symbol, and Conversion factor (defined from the base unit, e.g. the conversion factor for grams is 0.001xkg), then click the check mark to save the new unit
4. To edit or archive an existing unit, hover over the row, then select either the Archive or Edit icons as desired

Note: If you archive a unit that is referenced in a schema field, the associated field will be automatically archived

Create a dropdown list

Dropdown lists are reusable value sets that can be referenced across multiple schemas. You can use dropdown lists to standardize how users enter structured values like organism type, status, or method. By centralizing these values, dropdowns improve data quality, simplify updates, and enable consistent filtering and reporting.

Before creating schema fields that reference dropdown values, you’ll need to configure dropdown lists. Users must have Registry admin access to create or edit dropdown lists. To configure a dropdown list:

1. Go to Registry Settings and find Dropdowns from the menu on the left side
2. Click Create or select an existing list
3. If creating a new dropdown, give it a unique name (e.g. Organism Type) and provide the options by clicking the + next to the Options section
   1. To add multiple dropdown options, click Import Options and enter each value on a separate line in the text box (e.g. E. coli, Yeast, CHO), then click Import Options
4. If you’d like to rearrange your options in alphabetical order, click Alphabetize
5. Add, edit, reorder, or archive the values in the list. Some changes such as reordering options save automatically. Other actions like editing an option require you to save changes by clicking the ✓ icon, or discard changes by clicking the ✕ icon. These updates apply to all fields using that dropdown

If creating a new dropdown, click Create to save

Once your dropdown is created, you’ll be able to reference it when adding a dropdown field to your schemas.

Schema overview

Schemas define the structure of your data in Benchling. They can represent materials, data, storage methods, or tasks. Schemas control how data is captured, stored, and linked across the platform. Each schema consists of fields - like text, dropdowns, entity links, or unit-aware numbers - that define the information users must enter.

Schemas are central to the data model in Benchling. By configuring schemas, admins can enforce structure, ensure consistency across entries, and enable rich search and reporting capabilities.

Benchling supports different types of schemas depending on the application including:

• Registry Schemas – Registry schemas describe categories of samples and chemical solutions, which can represent theoretical concepts (e.g., plasmids, cell lines) or physical items (e.g. plasmid lots, cell banks). There are several types of Registry schemas, each with scientifically aware characteristics:

Depending on your organization’s licensing, not all of the Registry schema types may be available in your tenant

• Inventory Schemas – define physical inventory formats for tracking and sample placement. There are several types of inventory schemas:

• Result Schemas – Result schemas define the structure of experimental and assay data.
• Workflow Schemas – Task schemas define how work is requested or executed across teams using the Workflows application
• Automation Schemas – Run schemas define the structure of data capture for instrument integrations and high throughput tasks. Connection schemas define the structure and permissions for instrument data connections
• Study Schemas – define the structure of data capture for Studies

All schemas are created and managed through Feature Settings, and their configuration determines what users see and interact with throughout the platform. Registry and Inventory schemas are governed by Registry permissions, while Result, Workflow, Automation, and Study schemas are governed by tenant-level permissions.

Create a new schema

Before creating a schema, it's helpful to first configure any dropdown lists or unit types your schema fields will reference. For example, if you plan to include a dropdown field for 'Organism' or 'Status,' or a unit-aware field for 'Concentration,' you’ll want to define those lists and unit types in advance. This ensures the schema fields are configured correctly and consistently.

You can link schemas using Entity Link field types to define relationships between records - for example, connecting a derived clone to its parent cell line. These relationships enhance data traceability and support structured workflows across applications.

For a full list of configurable field types that can be used in schemas, see our Field Types chart on docs.benchling.com. Not all field types are available for all schema types; refer to the Supported Resources column to see where each field type can be used.

For more about creating specific schemas, use the articles linked above. While creating each type of schema may have some specific steps, generally to create a new schema:

1. In the bottom-left corner, click your avatar icon, then hover over Feature Settings, then select the appropriate option for the schema that you want to create (e.g. Registry settings or Result schemas)
2. From the appropriate schemas page, click Create
3. Define the schema's name, prefix (if relevant), and other information (e.g. entity type for Registry schemas)
4. Define each schema field’s name and definition, optionally, use the checkboxes to indicate if the field is required, multi-select, and/or (for Registry schemas) a Parent link
5. Click Next to configure schema access policies
6. Click Save

Note: For Result, Run, and Workflow schemas, you can set “Computed field (snapshot)” fields after the schema has been created that lookup defined information from related schemas at the point in time that a user stores information in the schema. For Registry schemas, reach out to Benchling Support to configure Computed Fields

Set display precision in structured tables 

You can define display precision for decimal fields in Registry and Result schemas. These settings control how values are displayed throughout Benchling, including in Registry and search. In Notebook tables, display precision controls how values appear after they are submitted. The orignial value entered into tables is retained and used in formula evaluation. Formula evaluation does not use the precision display value for calculations. This approach ensures that calculations maintain accuracy even when the UI rounds the values for presentation.

If the Schema display precision setting is changed at any time, all data outside of the Notebook will abide by this new precision based off of the original input value which is retained.  Historical Notebook tables will not be changed, the new precision value is only applied on table submissions moving forward.

Note: These schema settings differ from the table cell display precision that can be placed on specific Notebook table cells directly by selecting the target column and using the settings icon in the table formatting bar to set precision.

Configure display precision for Registry schemas

1. Highlight the decimal field where display precision should be applied
2. Click the gear icon and select Set decimal precisions to set to the desired number of decimal places 

Configure display precision for Results schemas

1. Open the result schema where display precision should be applied and click Edit as JSON
2. Find the float field you would like to modify and add the JSON script "decimalPrecision" : [number]
3. Click Update to save the changes 

Edit existing schema fields

As your processes evolve, you may need to update schemas to reflect new data needs. You can add new fields, rename existing ones, or update field configurations while preserving past records. This helps your schemas stay aligned with scientific processes without interrupting data capture.

Before editing an existing schema, you should consider any effects to existing data and ensure proper change management to avoid data loss or confusion. Besides editing an existing field, you could alternatively archive the existing field and create a new one or create a new schema version.

You can generally make changes to Registry schemas to make fields required or to change field type, except for number fields where units have been defined. Existing entities that do not meet the updated schema requirements will be flagged as out of validation and can be updated or the validation flag can be overridden for desired entities. For other schema types (e.g. Results, Runs), you can’t make breaking changes once data has been captured in the schema, and you’ll be required to create a new field to change the field type or to create a new schema to add required fields.

If you intend to create a new schema or new field on an existing schema, keep in mind that it cannot share a name with an existing schema or another field on the same schema. If you want to reuse a name, you should rename the former schema or schema field (including the system name) prior to archival.

Please reach out to support@benchling.com for additional help in these areas. 

To modify an existing schema:

1. In the bottom-left corner, click your avatar icon, then hover over Feature Settings, then select the appropriate option for the schema that you want to edit (e.g. Registry settings or Result schemas)
2. From the appropriate schemas page, click on the schema you wish to edit
3. To add a field, click the + icon
4. To edit a field, hover over it and click the pencil icon
5. Make the necessary changes and click ✔ to save
6. To reorder schema fields, hover over the field you need to move, then click and hold the perpendicular arrows that display to the left of the field, then drag the field to the desired place

Archive schemas and fields

Over time, your team may outgrow certain schemas or fields, or move to newer versions. Through archival, you can retire schemas or individual fields from active use without deleting historical data. This preserves system performance, reduces clutter, and maintains a clean experience for end users.

Archiving hides schemas or fields from active use without deleting data.

To archive a schema:

1. Navigate to the Entity schemas menu of Registry Settings
2. Hover over the schema you wish to archive and click the Archive icon
3. Select an archive status and click Archive to confirm the action

To unarchive a schema, adjust the schema filter to include archived schemas, then hover over the schema and click the Unarchive icon.

To archive a schema field:

1. In the schema configuration page, locate the field to archive
2. Click the Archive icon next to the field
3. Select an archive status and click Archive to confirm the action

To unarchive a schema field, click Show archived fields on the schema settings page, then hover over the field and click the Unarchive icon.

You will not be able to archive schema fields in the following situations:

• There are un-archived references to the field (including computed fields)
• The field is used in a naming template or uniqueness constraint

Manage permissions and access 

Proper permissions ensure data security and appropriate access levels. In Benchling, different user roles have different levels of control across the tenant. Understanding these roles is critical to managing administrative responsibilities and limiting access where necessary.

Role-based permissions

User roles complement object-level and schema-level access policies. For example, a user may have Tenant Admin rights and still need Registry Admin rights to configure schema permissions. User roles provide the following access:

*Organization Admin is scoped to a single organization, not the tenant, but is listed here for context.

**This allows users with this access to add themselves to an organization or team, even as an admin of the group. Once added, the user is a regular member or admin of that group, including access to data granted to the group.  Also, some customers have a setting enabled to automatically give the Tenant Admin role to anyone who is given Organization Admin access, which normally only another Tenant Admin can do but under these circumstances could be done by anyone with the access to manage organization membership and roles.

Registry permissions

Registry-level permissions control who can view, access, and modify Registry configurations and settings, including Registry collaborators, Entity schemas, Entry schemas, Inventory schemas (Containers, Plates, Boxes, and Locations), Dropdowns, Printers, and Label templates.

Permission levels

The table below displays the actions users can perform at the project or folder level with default general access policies.

Note: other schema types are governed by Organization Admin status; Teams can be granted access to create (but not edit) Run and Result schemas and to create and edit Workflow and Request schemas on the Team Settings page.

Set Registry permissions

You must have Registry admin permissions to update Registry permissions.

1. In Feature Settings, click Registry Settings
2. In [Org] Registry settings, click General
3. Add new collaborators in the top search bar by searching for user, email, team, organization, or app. Specify the general access policy that should be granted to the user in the right dropdown, then click Add
4. To update Registry permissions for existing users, use the dropdowns under Access Policies
5. To remove user permissions, click the … icon next to the collaborator and click Remove
6. Click Save to apply the permissions

Determine Registry schema permission source

Registered entities from each Entity schema can use either registry-level or project-level permissions. To change a schema’s permission source, contact Benchling Support.

1. In Feature Settings, click Registry Settings
2. Open the desired schema
3. Under Access Policies, scroll down to the Registering Entities section to check whether the schema uses Registry or Project permissions

Schema permissions

Schema permissions provide granular control over how users interact with schemas and their objects as defined in the table below. Schema permissions and access policies are designed to align with higher-level Registry and project permissions, not override them.

Permission levels

The table below displays the actions users can perform at the schema level with default  schema access policies. Schema access policies cannot be customized.

*Schema objects might additionally depend on higher-level Registry or project permissions.

Configure default schema permissions

Organization admins can configure default schema configurations, which automatically apply to all newly created schemas in an organization and can be set for Connection, Entity, Fieldset, Result, Run, and Study schemas.

1. In Feature Settings, click Access Policies
2. In the menu, click Schema Access Policies, then click the Settings tab
3. Select the organization from the Organization dropdown menu, then select the schema type from the list that displays below it
4. Search for users, teams, or organizations under Default Options, then click Add
5. In the Schema Access Policy column, select the default schema access policy for each collaborator
6. Click Save

Set individual schema permissions

Schema admins can configure permissions on individual schemas.

1. In Feature Settings, click Registry Settings
2. In the menu, click on the schema type that you want to update, then click the individual Connection, Entity, Entry, Run, Result, or Fieldset schema to update
3. Click the Access Policies tab
4. Add new collaborators in the top search bar by searching for user, team, organization, or app. Specify the general access policy that should be granted to the user in the right dropdown, then click Add
5. To update schema permissions for existing users, use the dropdowns under Access Policies
6. To remove user permissions, click … next to the collaborator and click Remove
7. Click Update Collaborators to apply the permissions

Customize access policies

The default general access policies that Benchling provides are:

• Read - can view, but cannot make changes
• Append - can create data, but cannot edit
• Write - can view, create, and edit
• Admin - can view, create, edit, and manage

For more tailored access control, tenant admins can customize policies for specific data types or workflows. Read access is always granted for every item type in a policy.

1. In the bottom-left corner, click your avatar icon, then hover over Feature Settings, then click Access Policies
2. To edit an existing access policy, click the desired policy. To create a new access policy, click the + button next to the Name field in the table header, select the existing access policy that you want to clone, name your new access policy, then click Save
3. Set individual actions for each listed action (grouped by item type, e.g. Entities, Notebook entries) as:

• Granted
• Not granted
• Granted to author (user can act only on items they authored)

5. Click Save when finished; changes take effect immediately
6. To delete an access policy, hover over the policy you want to delete and click the trash icon that appears

Project and folder permissions

Projects are the foundation of access control for most items in Benchling. Permissions on a project determine who can view, create, and modify its contents. Each project must have an owner, and for many tenants, the owner must be an organization. If the owner is an organization, all admins of that organization will have admin access to the project. Project admins can assign additional collaborators permissions to the project. Each user or team can be granted one of the following levels:

• Read: Can view all project contents but cannot make changes
• Append: Can create items within the project
• Write: Can create, edit, and archive items within the project
• Admin: Can manage collaborators, modify project settings, and archive content

Permissions are cumulative; for example, if a user is added with Read access and also belongs to a team with Write access, they will have Write access. 

Folders inherit permissions from the parent project but can also have more specific permissions added at the folder level. If a user has access to a folder but not the parent project, only the folder displays in the Projects panel of the workspace. 

Folders can never be less permissive than their parent project. If a user has Write access to a project, they will have at least Write access to all subfolders in that project. We recommend applying the least permissive access policies to projects and granting additional access to their contained folders, as needed.

Note: Folder permissions are currently not supported in the warehouse or Insights dashboards.  No user will ever see data they don't have access to, but if they don't have at least Read access at the project level they will not be able to find the objects from folders they have access to in the warehouse or Insights dashboards.  All other features like search, Insights Analyses, and the Projects panel will work as expected.

Enable or disable folder permissions

To enable or disable folder permissions, you must be a Tenant Admin.

1. Open the Tenant Admin Console
2. Click Settings, then click Permission Controls
3. Turn on or turn off folder permissions as appropriate

Note: Folders must have permissions removed before disabling folder permissions tenant-wide. If you have admin access to the relevant folders, Benchling will remove any existing folder permissions as part of turning off folder permissions. If you don’t have admin access to those folders, you’ll get a message indicating which folders need to be updated and no changes will be made.

Permission levels

The table below displays the actions users can perform at the project or folder level with default general access policies.

Set project and folder permissions

1. Click the briefcase icon to open the Projects panel
2. Right-click on the project or folder name and click Manage access. Alternatively, open the desired project or folder, click the gear icon next to the project or folder name, then click Manage access
   
   

3. Add new collaborators in the top search bar by searching for user, email, team, organization, or app. Specify the general access policy that should be granted to the user in the right dropdown, and click Add
4. To update project permissions for existing users, use the dropdowns under Access Policies. To update Folder permissions for existing users, use the top search bar to search for the collaborator, select the general access policy that should be granted in the right dropdown, then click Add
5. To remove user permissions from a project or folder, click the … icon next to the collaborator and click Remove. At the folder level, you can only remove user permissions that were granted at the folder level
6. Click Done if you are setting permissions for a new project or folder or Save if you are updating permissions for an existing project or folder
   
    

Legacy data import

Legacy data import is the process of bringing historical records, such as samples and containers, into your Benchling tenant from previous systems or spreadsheets. This step is typically completed after your users, teams, schemas, and permissions are fully configured so that the incoming data has the correct structure and access controls. Importing legacy data helps you maintain continuity and centralize your records in Benchling without losing past context.

See Import Registry data in bulk or upload inventory information using spreadsheets for instructions for bulk importing legacy data into Registry or Inventory schemas.

Configure audit logs

Audit logs are documents containing the histories of objects, like entries, entities, tables, insights, etc., and include all the information necessary to understand how the object has changed over time. You can download audit logs as .csv or .pdf files. To ensure compliance, most audit log columns aren't configurable. However, you can customize some columns to help with organization and readability.

You can customize audit logs by adding or removing optional columns. You can also choose how some columns display, like timestamps. To customize your audit logs:

1. Click your avatar and navigate to the Tenant Admin Console
2. Click the Settings tab, then select Configurations
3. Customize fields using their respective drop-down menus in the Data Management section
4. In the Audit log columns section, optionally click Select columns to export, then select any non-required columns to display or not display in audit log exports. Required columns can't be deselected

The table below describes each column in the audit log, what they represent, and if the column is required for compliance. Optional columns can be added or removed from audit log exports. Columns marked with an asterisk ( * ) are customizable.

Export audit logs

You can view the history of an object by exporting its audit log. To export an audit log:

1. In the expanded view of an application, select the entities or entries you want to audit
2. Click Export, then click Export Audit Logs
3. In the drop-down menu, select the audit log format. You can choose to export the file as a .csv or .pdf
4. Click Export to generate an audit log, including archive information

Frequently asked questions

Q: Are unit symbols case sensitive?

A: Yes. Unit symbols are case sensitive so that you can configure units where case is used to represent different concepts (e.g. nm for nanometers and nM for nanomolar.)

Q: Can I set access policies for Inventory or Workflow schemas?

A: No. It is not possible to set access policies for Inventory or Workflow schemas. It is possible to grant permissions to update workflow schemas at the Team level using the Schema Permissions checkbox on the Team’s Settings page.

Q: Is there a maximum limit to the number of entities that can be bulk imported?

A: Yes. There is a limit of creating 5k entities AND containers. This means if you are registering entities and transferring them into containers at the same time (e.g. has 'Transfer entities to new or existing containers' checked during import), the limit would be 2.5k spreadsheet rows (entity + container creation). Please be mindful that Benchling's performance may be dependent on the complexity and the volume of this entity import.

Q: How do I add the units that were previously available in the Inventory tables back to my tenant?

A: As part of the units rollout, unused units per tenant were cleaned up from the list of quantities and concentrations that were previously available. Many of those units are available as preset units that can be added via the Unit Dictionary Wizard by your tenant admin. 

The gif below demonstrates how preset units (ex. cell counts like "x10^7 cells" or others) can be added to the list of available inventory quantity or concentrations in the unit dictionary.

Q: My inventory table is erroring due to missing Concentrations or Quantity units. What do I do?

A: Please see the "How do I add the units that were available in the Inventory tables back to my tenant?" question above.

Q: I'm getting the error "Could not find Unit for "{symbol}". What do I do?

A: If you see a red toast that says "Could not find Unit for "{symbol}" with a specific unit noted, please ask your tenant admin to add the unit to the Unit Dictionary.

Q: Can I migrate my units with Config Migration?

A: Yes, you can use the configuration migration tool to migrate all components of the unit dictionary as well as unit-aware fields on Result schemas, entity schemas, recipes, etc.