> 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/how-to-create-custom-permissions.md). # How to create custom permissions This short tutorial shows how to create custom permissions to use in the PIM. ## Creating a custom permission To create a custom permission navigate to Settings > General > Permissions.

Click '+ Create permission' in the top right corner. This will take present you with the 'Create permission'-page.

Give the new permission a concise name, a description and place it in a permission group that fits. In this case we have placed it in the permission group 'Products' as the permission will be used to limit view access on a product model. Having given the permission a name, description and permission group click 'Save' to save the custom permission. --- # 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/how-to-create-custom-permissions.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.