====== Setting up permissions ======

MCServer comes with built in groups and permissions management and is really easy to configure.

To manage users and groups, MCServer uses the two files ''groups.ini'' and ''users.ini''.

===== Setting up groups =====

By default MCServer comes with ''groups.ini'' with these contents:
<code ini>
[Admins]
Permissions=*
Color=c

[Mods]
Color=5
Inherits=Vips
Permissions=core.time,core.item

[Vips]
Permissions=core.teleport
Color=2
Inherits=Default

[Default]
Permissions=core.help,core.playerlist,core.pluginlist,core.spawn
Color=7
</code>

The group names are declared as sections, ''[GroupName]'', and cannot have spaces in them. The sample comes with the four groups ''Admins'', ''Mods'' and ''Vips''
Groups can have a color, colors range from 1 to f (0123456789abcdef), [[http://www.minecraftwiki.net/images/4/4c/Colors.png | this image]] shows which letter represents which color.

===== Setting up users =====

By default MCServer comes with ''users.ini'' with these contents:
<code ini>
[SomeAdmin]
Groups=Admins

[FancyModerator]
Groups=Moderators

[ImportantPerson]
Groups=Vips
</code>

The player names are declared as sections, ''[PlayerName]''. The sample comes with the three users ''SomeAdmin'', ''FancyModerator'' and ''ImportantPerson''
Each user can contain several groups separated by commas.

===== Permission syntax =====
MCServer uses a hierarchical structure to define permissions. Each permission can have several child permissions.

Let's use these permissions for examples
<code>core.help
core.pluginlist
core.teleport
core.item</code>

When you give a user the permission ''core.pluginlist'' the player will be able to request a list of plugins in game. When you give a user the permission ''core.*'' the user will have all possible permissions in the ''core'' namespace. When you give a user the permission ''*'' the user has all possible permissions in any namespace.

Ask the creator of the plugins you are using for the permissions it has.