> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-set-up-default-list-configurations-for-a-user-group.md).
# How to set up default list configurations for a user group
Learn how to set up default list configurations for a user group.
### Getting started
To set up default configurations for a user group, open **User Management** from the top menu.
Select the **User groups** tab in the left-hand menu. Then select the user group that needs default list configurations.
Overview of all user groups.
In the selected user group's settings, select the **Default setup** tab above **General settings**. Here, you can configure the default filters and columns.
Inside the user group settings.
### Configuring the default columns and filters
You can configure default columns and filters for different entities in each user group. Add multiple configurations, but only one per entity.
The default setup page on a user group.
When you finish configuring the user group, click **Save**.
### Set up catalogue-specific columns
To use catalogue-specific columns as the defaults, go to **Settings** → **General setup**. Enable **Enable catalogue-specific columns**. This adds a catalogue picker to the column configuration. You can then specify columns for each catalogue.
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
### What the user group sees
Users in the configured group now see the default column selection when they open the PIM search.
The default columns displayed in a user's PIM search.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-set-up-default-list-configurations-for-a-user-group.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
