> For the complete documentation index, see [llms.txt](https://opuszek.gitbook.io/itemblocker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://opuszek.gitbook.io/itemblocker/integrations/permission-plugins.md).

# LuckPerms and other permission plugins

ItemBlocker uses normal server permissions, so it works with LuckPerms and any other permission plugin without setup. Every permission is listed on [Permissions](/itemblocker/reference/permissions.md).

## Examples with LuckPerms

Let moderators manage rules:

```
/lp group moderator permission set itemblocker.admin true
```

Let VIPs wear elytras although a rule blocks them:

```
/ib block elytra actions:armor bypass:vip.elytra
/lp group vip permission set vip.elytra true
```

Let one group ignore a whole preset:

```
/lp group builder permission set itemblocker.bypass.preset.survival true
```

Only in one world, with a context:

```
/lp group vip permission set itemblocker.bypass.use true world=arena
```

## Operators

Operators get `itemblocker.bypass` by default and ignore every restriction. To have operators follow the rules, deny it:

```
/lp user <name> permission set itemblocker.bypass false
```

or set both `bypass.enabled: false` and `bypass.per-action: false` in [config.yml](/itemblocker/reference/config.md), then run `/ib reload`.


---

# 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://opuszek.gitbook.io/itemblocker/integrations/permission-plugins.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.