> For the complete documentation index, see [llms.txt](https://groupsecurity.mikart.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://groupsecurity.mikart.eu/main/security-engines.md).

# Security Engines

### Block Commands Before Login (recommended)

```yaml
# What security engine to use. Possible values are listed and explained in the documentation.
type: 1
```

This mode is most suitable for all servers since it makes the player have the group before login so the other players can see the prefix the player has.

{% hint style="info" %}
This mode blocks commands before login.
{% endhint %}

### Add group after login <mark style="color:yellow;">(new)</mark>

```yaml
# What security engine to use. Possible values are listed and explained in the documentation.
type: 2
```

This mode adds the permissions after login. If the prefix is defined in the group, it will not show up. However, it is recommended to use type 1 instead since this is made mostly to support some types of server configurations.

{% hint style="warning" %}
A permission plugin like LuckPerms is required for this mode.
{% endhint %}


---

# 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://groupsecurity.mikart.eu/main/security-engines.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.