Fieldset permissions reset by Team management actions

Fabio
Fabio
  • Updated

What happened?

Benchling identified and resolved an issue where, under specific Team management actions, fieldset schema-level permissions could be unintentionally reset. As a result, some users may have received elevated permissions to view and/or edit fieldset configurations. The change was configuration only (no data loss or modification). The issue only impacted the ability to view fieldsets, not any schemas using this fieldset or any associated entities. All changes were correctly recorded in audit logs. 

 

Key Definition

Fieldset: A Fieldset in Benchling is a reusable group of fields that standardizes data across multiple registry schemas. It defines a shared set of metadata that can be applied to different schemas, creating a category that links them. Fieldsets are configured at the Organization level and have specific schema-level permissions that control who can view or edit their configuration.

 

What is the impact?

When users performed certain Team management actions, fieldset schema-level permissions across an Organization could have been overwritten with a standardized set of access policies in following cases:

  • Creating a Team via the “Teams” tab in the Tenant Admin Console with the “Schema Permissions" checkbox enabled 
  • Editing settings of a Team, including enabling/disabling the “Schema Permissions” checkbox or updating Team information (such as Team name) 

    Team settings page with Schema Permissions checkbox selected

The fieldset schema-level permissions reset to following access policies:

  • Admins of owning Organization: Admin Policy
  • Members of owning Organization: Create Policy (functionally grants Read access)
  • Members of any Team with “Schema Permissions” enabled: Admin Policy 
Example of Fieldset Schema-level permissions

 

Resolution Timeline

  • Non-Validated Cloud: September 24, 2025 
  • Validated Cloud Preview: October 15, 2025
  • Validated Cloud Production: October 22, 2025

 

Who is Impacted

Benchling is proactively notifying customers who are impacted by this issue. If you have questions or believe you have been impacted, please reach out to support@benchling.com.

 

What to do if Impacted

Benchling recommends reviewing fieldset schema-level permissions and adjusting configurations as needed. An impact assessment identifying affected fieldsets is available upon request.

Was this article helpful?

Have more questions? Submit a request