# Permissions

STB will work with any superperms-supporting permissions plugin. The following permission nodes are understood:

## General Nodes

| Node           | Description                                   | Default |
| -------------- | --------------------------------------------- | ------- |
| stb.admin      | Gives full permission to do anything with STB | op      |
| stb.access.any | Allows access to private block GUI's          | op      |

## Command Nodes

| Node                     | Description                                                        | Default |
| ------------------------ | ------------------------------------------------------------------ | ------- |
| stb.commands.charge      | Allows the `/stb charge` command to be used                        | op      |
| stb.commands.debug       | Allows the `/stb debug` command to be used                         | op      |
| stb.commands.getcfg      | Allows the `/stb getcfg` command to be used                        | op      |
| stb.commands.give        | Allows the `/stb give` command to be used                          | op      |
| stb.commands.recipe      | Allows the `/stb recipe` command to be used                        | player  |
| stb.commands.rename      | Allows the `/stb rename` command to be used                        | player  |
| stb.commands.rename.free | Allows the `/stb rename` command to be used for no experience cost | op      |
| stb.commands.save        | Allows the `/stb save` command to be used                          | op      |
| stb.commands.setcfg      | Allows the `/stb setcfg` command to be used                        | op      |
| stb.commands.show        | Allows the `/stb show` command to be used                          | op      |
| stb.recipebook.freefab   | Allows free fabrication of items via the recipe book               | op      |

For full documentation of what each command does, see [Commands](/mctantrum-wiki/slimefun/addons/sensibletoolbox/commands.md).

## Item-Specific Nodes

These nodes exists for every known item ID - see [Item Reference](/mctantrum-wiki/slimefun/addons/sensibletoolbox/item-reference.md) for a full list of item IDs.

| Node                          | Description                                                               | Default |
| ----------------------------- | ------------------------------------------------------------------------- | ------- |
| stb.interact.{item-id}        | Allows an item to be used (left- or right-clicking with the item in hand) | true    |
| stb.interact\_block.{item-id} | Allows a placed block to be used by right-clicking it                     | true    |
| stb.place.{item-id}           | Allows the item to be placed as a block                                   | true    |
| stb.break.{item-id}           | Allows a placed block to be broken                                        | true    |
| stb.craft.{item-id}           | Allows the item to be crafted (*v0.0.4+*)                                 | true    |
| stb.allow.{item-id}           | Parent node giving all of the above nodes (*v0.0.4+*)                     | true    |

For example, to prevent a player (or permission group) breaking Redstone Clocks, add the permission node **stb.break.redstoneclock = false** to the player or group. The syntax here obviously depends on the permission plugin you're using.

The default permissions allow all actions to be taken on/with every STB item block.

For block protection, larger servers will probably be best served by using a dedicated protection plugin such as WorldGuard but these permissions exist as another protection option for specific STB block and item types.


---

# Agent Instructions: 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:

```
GET https://reasonfounddecoy.gitbook.io/mctantrum-wiki/slimefun/addons/sensibletoolbox/permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.