# Allow Fragment Configuration FieldSets to Be Collapsed by Default

**URL:** <https://discuss.liferay.com/t/allow-fragment-configuration-fieldsets-to-be-collapsed-by-default/424>\
**Category:** Product Ideas\
**Tags:** not-priority, fragments\
**Created:** [March 16, 2026, 1:41pm UTC](https://discuss.liferay.com/t/allow-fragment-configuration-fieldsets-to-be-collapsed-by-default/424 "2026-03-16T13:41:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jconrad](https://avatars.discourse-cdn.com/v4/letter/j/85e7bf/32.png) [@jconrad](https://discuss.liferay.com/u/jconrad)\
**Post date:** [March 16, 2026, 1:41pm UTC](https://discuss.liferay.com/t/allow-fragment-configuration-fieldsets-to-be-collapsed-by-default/424/1 "2026-03-16T13:41:26Z")

</div>

**What is the problem you are trying to solve?**

Fragments allow developers to define custom configuration panels using the `fragment json` window. These configurations support grouping fields using `fieldSets`, but all fieldSets are always **expanded by default** when users open the fragment settings panel.

This becomes problematic when fragments contain a large number of configuration groups. Content editors must scroll through long lists of configuration blocks.

Being able to collapse a fieldSet by default would improve:

- **Usability** for content editors

- **Readability** of complex configurations

- **Organization** of large fragments

**What is your proposed solution? (optional)**

Introduce a new optional property “collapsedByDefault“ in fragment `fieldSets` such as:

```json
{
  "label": "Card",
  "collapsedByDefault": true,
  "fields": [
    ...
  ]
}

```
