> 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 ## Creating a custom permission To create a custom permission navigate to Settings > General > Permissions.

'Permissions'-page

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

'Create permissions'-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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` 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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.