> 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-modes.md).

# Security Modes

These are all the security modes, as in the type of login staff needs to use to access the permissions. This is not the same as the Security Engine.

### Pin

{% hint style="warning" %}
Pin codes aren't as safe as other methods if the database file is exposed, and the pin can be read in plaintext. But if someone has access to the machine, they have full access anyway. All methods in GroupSecurity are ridiculously safe anyway in player standpoint.
{% endhint %}

A pin consists of 4 digits. It can only be 4 digits, not more or less.  This mode offers really easy and fast logins.

### Password

A password can be any length wanted, any characters used. It will be securely hashed in the database. This might take a bit longer for people to login.

### 2-Factor Authentication <mark style="color:yellow;">(premium)</mark>

The safest mode of securing groups and permissions is 2-factor authentication. To use this mode you need to follow these instructions:

1. As console, or permissioned player run the command: `/gsadd`


---

# 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-modes.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.