> 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-set-up-permissions.md).

# How to set up permissions

Permissions allow you to limit access or editing rights on data models.

### What are permissions & permission groups <a href="#permissions-and-permission-groups" id="permissions-and-permission-groups"></a>

A range of permissions exist by default in Struct PIM, and they are divided into permission groups. A permission defines an access right described by its name ranging from access to viewing products to configuring data models.

In configurations of global lists, catalogues and product structures, new permissions can be defined to limit users' access to a specific part of the data models.

{% embed url="<https://vimeo.com/1142450352?fe=ec&fl=ip>" %}
Permissions in Struct PIM (duration 02:47 min)
{% endembed %}

### Guides covering permissions

* [How to set up permissions on tabs, sections and properties](/tutorials/guides/how-to-set-up-permissions/how-to-set-up-permissions-on-tabs-sections-and-properties.md)
* [How to create custom permissions](/tutorials/guides/how-to-set-up-permissions/how-to-create-custom-permissions.md)


---

# 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-set-up-permissions.md?ask=<question>&goal=<user_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.