> For the complete documentation index, see [llms.txt](https://krankey.gitbook.io/partybeast/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://krankey.gitbook.io/partybeast/user-commands/limit.md).

# /limit

**Command**

```
/limit #
```

Typing the `/limit #` command will limit the room to the number of users specified.\
Users should replace `#` with number of users they wish to limit their channel to.\
Setting the number to 0 will remove the limit.

When a room owner has successfully set the limit on the room they will receive a message like below:

![](/files/OE9AJAlP5pEnxGsDvw7o)

**Required Permissions**

In the event that PartyBeast does not have the correct permissions to make the changes required to kick a user or change the permissions to ban a user you will receive the following error message:

![](/files/ri00dNHBrMLgwUWS345I)

In this case you should check that the PartyBeast **role** has the following permissions available on the **category** where new channels are created.\
Be aware that this should apply to any roles which you have assigned PartyBeast:

* View Channel
* Manage Channel
* Manage Permissions
* Connect
* Manage Members


---

# 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://krankey.gitbook.io/partybeast/user-commands/limit.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.