A CMS Collection List can be locked on your Webflow site if it's being used in a way that restricts changes to the Collection’s structure or fields.
1. Embedded on Static or Symbol Pages
- If a Collection List is placed on a static page or inside a Symbol, Webflow restricts some CMS management options to avoid breaking existing layouts.
- You need to remove the Collection List from the static page or Symbol in order to edit the CMS Collection’s structure (like adding/removing fields).
2. Referenced in a Collection Page
- If your CMS Collection is referenced inside other Collection Pages, that dependency can lock editing of the referenced fields.
- To identify this, go to CMS → Collection Settings, and Webflow will usually notify you with a message like “This field is used in...” and list the dependencies.
3. Used in Conditional Visibility or Bindings
- CMS fields that are used in Conditional Visibility rules, Filters, or binding for elements like buttons or text may also lock editing of the field or prevent its deletion.
- You must remove those bindings across your project before making structural changes to that field.
4. Linked to Ecommerce or Membership Features
- If the collection is tied to Ecommerce (Products, Categories) or Webflow Memberships, it will be partially or fully locked based on system usage.
- You cannot freely change built-in system collections like “Products” or “Users” used in memberships.
5. Multi-Reference or Reference Constraints
- If a Reference or Multi-Reference field connects your locked Collection to another Collection, Webflow enforces a relationship that must be dismantled to unlock field editing.
- You must either remove the reference field from the other Collection or break the connection temporarily.
Summary
A Webflow CMS Collection List is locked when it's in use across your site in static pages, symbols, conditional rules, or linked to system features like Ecommerce or Memberships. Inspect where it's used and remove dependencies to unlock editing options.