ACL Tutorial/English

From Mumble Wiki
< ACL Tutorial
Revision as of 16:03, 2 August 2007 by Javitonino (talk | contribs) (Started writing an illustrated tutorial to ACL)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

ACL tutorial

This tutorial will help you understand how permissions work on Mumble. Details about this topic can be found in ACL and Groups, where there are some examples, descriptions of special groups, etc.

What we are going to do

We are going to set a server, with a General chat channel where everyone can talk. We are also creating a Custom channels channel where anyone who is authed can create and administrate his own channel. Then, as a normal authed user, we will create a couple of channels for a FPS game where people can talk either to their team or to everyone just by pressing one key.

Enough talking, let's get to work.

Setting permission for the whole server

First, we will need to set up a password for the SuperUser. If you haven't done that yet, you can do it by typing this at a console/command prompt:

murmur -supw somepassword

Then, we open Mumble and connect to the server using SuperUser and the password we have just set. You should be looking at something like this now:

Let's start with the permissions. Open the ACL editor, you can do thi will use the menu alternative. Once we are there, you can see a windows with two tabs. The first one is for defining people who is in a group, etc. The second one is used to assign permissions to groups. Right now, in that tab, you should have two rules set:

  • The first one allows people on the auth group to create channels in the root channel and its subchannels.
  • The second one allows people in the group admins to Write, that means edit permissions.

For now, we will delete the rule related with the auth group by selecting it and clicking remove. We said that we don't want anyone in the root channel, as we will make a General chat channel for that. So we will add a rule to keep them out. To do that, click add, and click every checkbox in the deny column except the Traverse one.

The reason to leave traverse unchecked is because it will forbid people to enter this channel and subchannels. Since every other channel is a subchannel of root, this will effectively forbid people from entering any channel. So we leave it unchecked. It is not neccesary to mark the allow check, because Traverse is allowed by default. Default settings are:

  • Allow: Traverse, Enter, Speak and AltSpeak
  • Deny: Write, Mute/Deafen, Move/Kick, Make Channel and Link channel

If you are wondering, yes, we could have left Write, Mute/Deafen, Move/Kick, Make Channel and Link channel unchecked and they will still be forbidden. There is no reason to leave those rights denied as they will be by default. Now your screen should be looking like this (except that you have disabled some useless checks):

In Mumble, rules are applied from top to bottom. Right now, the:

@admins allow write

rule is useless as it will get over written by the

@all deny write ...

So we will have to fix it. Simply select the rule referring to all and click up. That should put that on top. You have now established some default settings for the whole server :)

Creating the General chat channel and setting its permissions

To be continued right now... I'm just saving just in case