How to Set Up GroupManager Permissions on a Minecraft Server

Overview

Plugins can add a huge range of commands and features to a Minecraft server, but most of those features need permission nodes before players can use them. GroupManager handles that work by letting you create groups, assign permissions, and place players into ranks.

GroupManager is commonly used on Spigot and Paper servers because it supports both command-based management and direct file editing. Commands are useful for quick changes, while configuration files are usually better for a full setup. Fewer blind edits, fewer surprises, and fewer moments staring at chat wondering why `/spawn` is being stubborn.

This guide explains how to install GroupManager, create ranks, add permissions, configure inheritance, format chat, and troubleshoot common problems.

Downloading GroupManager

1. Open the GroupManager page on Spigot and select Download Now.

1. If you are redirected to GitHub, find the release that matches your server version.
2. Expand Assets, then download the `GroupManager.jar` file.

1. Save the file somewhere easy to find, such as your desktop or downloads folder.

Installing the Plugin

After downloading the jar file, upload it to the `plugins` folder for your Minecraft server. The exact panel layout can vary, but the process is the same on most hosts.

1. Open the HolyHosting server panel and go to your file access or FTP area.

1. Log in with your server panel password if prompted.

1. Open the `plugins` directory.
2. Use the upload option and add the `GroupManager.jar` file.

1. Wait until the upload reaches 100%.
2. Return to the main server page, restart the server, then join to confirm the plugin loaded.

If the server has multiple profiles or instances, verify that you uploaded the jar to the active server profile. Uploading the plugin to an unused profile is a surprisingly efficient way to install nothing at all.

First Setup Choices

GroupManager can be managed in two main ways: in-game commands or configuration files. Commands are fine for small edits, such as adding one player to a group. For building several ranks with many permission nodes, editing the YAML files is usually clearer.

Before changing anything, gather the permission nodes from the plugins installed on your server. For example, EssentialsX Spawn commonly uses `essentials.spawn` to allow `/spawn`. Most plugins list permissions on their Spigot page, GitHub page, wiki, or documentation site.

It also helps to decide your rank structure before editing files. A simple survival server might only need `Default`, `Member`, `Moderator`, and `Admin`. A network-style server may need extra donor, staff, builder, or event ranks. Keep the first setup simple, then add complexity once the basics work.

Creating a Group in groups.yml

GroupManager includes default groups, but custom ranks are often cleaner for public servers. You can create groups with `/mangadd [group]`, but this section uses the file method.

1. Open your server file access area and log in.
2. Go to `plugins`, then open the `GroupManager` folder.

1. Open the path for your world, usually `worlds/[world name]`.
2. Edit `groups.yml`.

1. Under `groups:`, add a new group using this structure:

```yaml GroupNameHere: default: false permissions:

• []

inheritance:

• g:groupmanager_default

info: build: true prefix: 'Prefix Here' suffix: 'Suffix Here' ```

Repeat the same pattern for any additional ranks you want, such as `Member`, `Mod`, `Admin`, or `VIP`. Only one group should normally have `default: true`, since that is the rank new players receive when they first join.

The `build: true` value allows players in that group to build, assuming another plugin is not blocking placement or breaking. If you are creating a guest or jailed rank, setting this to `false` can be useful.

Adding Permission Nodes

A group is only useful once it has permissions. In `groups.yml`, replace the empty `[]` value under `permissions` with the nodes you want that rank to have.

Example:

```yaml permissions:

• essentials.spawn
• essentials.home
• essentials.sethome

```

Use one permission per line, keep the dash, and match the node spelling exactly. YAML spacing matters, so do not mix random indentation levels unless you enjoy debugging invisible formatting problems.

Wildcard permissions such as `essentials.*` may grant broad access, but use them carefully. They can expose commands you did not intend to give players. For staff ranks, broad permissions can be convenient. For normal players, specific nodes are safer and easier to audit later.

When all permissions are added, save the file.

Restart the server from the panel so GroupManager reloads your changes.

Using Inheritance

Inheritance lets one group receive permissions from another shared collection. This is useful when multiple worlds or ranks need the same base permissions. GroupManager includes several global groups by default, such as groups for common EssentialsX permission sets.

To create your own inherited permission group, edit `globalgroups.yml`.

1. Go to `plugins/GroupManager` in your server files.
2. Edit `globalgroups.yml`.

1. Under `groups:`, add a new global group:

```yaml g:custom_base: permissions:

• essentials.spawn
• essentials.home

```

1. Add or remove permission lines until the group has the nodes you need.

1. Save the file, then return to `groups.yml`.
2. Add the inheritance value under the target group:

```yaml inheritance:

• g:custom_base

```

Add more inheritance lines if the group needs several shared permission sets. Save the file and restart the server when finished.

Inheritance is especially helpful for rank ladders. For example, `Moderator` can inherit normal player permissions, while `Admin` can inherit both player and moderator permissions. That way, a basic permission only needs to be edited in one place.

Formatting Prefixes and Suffixes

GroupManager can store rank prefixes and suffixes for chat formatting. This is commonly used for labels like `[Admin]`, `[Mod]`, or `[VIP]`. Color codes are supported with the `&` symbol, so an admin prefix could look like this:

```yaml prefix: '&0[&cAdmin&0] &4' suffix: '' ```

The trailing space after the prefix is important because it separates the rank tag from the player name.

If prefixes do not appear in chat, make sure you have a compatible chat plugin installed. EssentialsX Chat is a common option. Other chat plugins may override GroupManager formatting, depending on their configuration.

For clean chat, keep prefixes short. A long rank name, several colors, and a suffix can quickly make messages hard to read, especially on smaller screens.

Assigning Players to Groups

Once your groups are configured, assign players with:

```text /manuadd [player] [group] ```

Replace `[player]` with the Minecraft username and `[group]` with the exact group name from `groups.yml`. To confirm a player rank, run:

```text /manwhois [player] ```

This displays the user information in chat, including the group they belong to.

If the command fails, check capitalization and spelling. Group names should match the configuration file, and the player must exist or have joined before on many server setups.

Useful Commands

File editing is best for larger setups, but commands are helpful for fast changes while in-game. Make sure your account is a server operator before using administrative GroupManager commands.

• `/mangadd [group]` creates a group.
• `/mangdel [group]` deletes a group.
• `/mangaddp [group] [permission]` adds a permission to a group.
• `/mangdelp [group] [permission]` removes a permission from a group.
• `/manuadd [player] [group]` assigns a player to a group.
• `/manudel [player]` removes a player from their assigned group.
• `/manwhois [player]` checks a player's current group information.

Follow the command format closely. A missing group name or misspelled permission node will usually fail without much ceremony.

For major rank changes, edit the files while the server is stopped or restart immediately after saving. This helps prevent command edits and file edits from overwriting each other.

Plugins That Pair Well With GroupManager

GroupManager becomes more useful when other plugins provide permissions worth managing.

• EssentialsX adds common server features such as homes, kits, teleportation, private messages, and spawn commands. Its Chat, Spawn, and Protect addons are often used alongside it.
• Vault is commonly required by economy and permission-aware plugins, especially when multiple plugins need to communicate cleanly.
• CombatLogX helps prevent players from leaving during combat and includes permissions for bypasses and feature control.
• PlaceholderAPI provides placeholders used by many plugins for player stats, server data, and dynamic text.
• MyCommand lets you create custom commands or aliases, which can then be restricted with permissions.
• EnhancedEnchants adds configurable enchantment behavior, including permissions for special actions or limits.
• MCRealistic adds survival mechanics like thirst, sickness, and block physics, with permissions for controlling access to features.

When adding a new plugin, check its permission list before giving access to players. Some plugins include separate admin, bypass, reload, or debug nodes that should stay limited to trusted staff.

Common Issues

GroupManager is not loading

Confirm the server is running Spigot or Paper, not vanilla Minecraft. Also check that your Minecraft version is supported by the GroupManager build you downloaded. If the plugin still does not load, make sure the jar file is inside the correct `plugins` folder and restart the server.

Configuration errors can also stop the plugin from loading. If the issue started after editing YAML files, review your most recent changes for spacing problems, missing colons, or broken indentation.

The server console is the fastest place to confirm the cause. Look for GroupManager errors during startup, then check the file and line number mentioned in the message if one is provided.

Prefixes or suffixes are not showing

Install and configure a compatible chat plugin. GroupManager can store prefix and suffix values, but chat output often depends on another plugin reading and displaying them. Keep the quotation marks around prefix and suffix values, especially when using color codes or empty fields.

If formatting appears but spacing looks wrong, add or remove spaces inside the prefix value. For example, `prefix: '&a[Member] '` includes a space after the closing bracket, while `prefix: '&a[Member]'` does not.

Permissions are not working

Check the formatting in `groups.yml`. Permission lines need the dash, correct indentation, and exact spelling. Save the file and restart the server after editing.

If a player is operator, they may already bypass normal permission checks. Remove operator status when testing rank permissions. Also confirm that any inheritance values exist in `globalgroups.yml` and are spelled correctly.

If only one plugin command is failing, confirm the permission node with that plugin's documentation. If every permission is failing, the issue is more likely GroupManager loading, YAML formatting, or the player being assigned to the wrong group.

Useful References

• GroupManager on Spigot
• GroupManager Wiki
• Minecraft server operator guide
• FTP and server file access guide