> For the complete documentation index, see [llms.txt](https://docs.tomorrowx.com/cap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomorrowx.com/cap/product-reference/managing-repositories/specifying-repository-rule-group-restrictions.md).

# Specifying Repository Rule Group Restrictions

If you are separating your user base into different skill levels, you can set the allowed rule groups to be used by the rule writer using the repository. This allows you to create a simpler user experience with more high-level rules for less technical rule writers.

<figure><img src="/files/nkJg5Xt9I0JWno49DcrG" alt=""><figcaption><p>restrictions</p></figcaption></figure>

Simply “untick” the **All** checkbox and you will be able to select specific rule groups that are appropriate for the given repository.

The groups available to you will depend on the settings against your role. Please note that even though an administrator may set allowed rule groups here, the user role settings take priority. So, the repository level settings should only be used to define subsets.


---

# 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.tomorrowx.com/cap/product-reference/managing-repositories/specifying-repository-rule-group-restrictions.md?ask=<question>&goal=<endgoal>
```

`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.