Plan requirement
| Subscription | Any plan |
| Access | WMS administrator |
ACL groups decide which WMS screens someone sees. Most systems use two: Default for everyone, IT Manager for the people who administer it.
The two groups you will work with
A Wildix PBX ships with Admin and Default. Admin has no limits and belongs to the system account; it is not a group people are put in. The administrator group in the table below is one we create for you, so on your system it may carry a different name.
| Can reach | Default | IT Manager |
|---|---|---|
| Call groups | Yes | Yes |
| Timetables | Yes | Yes |
| Phonebooks | Yes | Yes |
| Users | No | Yes |
| Add and remove users | No | Yes |
| Subscription plans | No | Yes |
IT Manager inherits everything Default has and adds to it, so you never lose access by moving someone up.
ACL does more than hide screens
The table above is about WMS. The same mechanism also governs what people can do in Collaboration or x-bees, and which kinds of number they are allowed to dial, so a group can permit national and mobile calls while blocking premium-rate ones. If somebody cannot reach a destination, this is where to look before suspecting the carrier.
Everything is allowed unless it is forbidden
That is the model: rules take things away rather than hand them out. It explains why a new permission usually means removing a restriction rather than adding a right.
Three exceptions, and they are the ones people ask about. Modifying presence, deleting calls and seeing voicemail are not allowed by default and have to be granted explicitly. So "I cannot see the voicemail" is usually not a fault and not a licence: it is a permission nobody switched on.
Handing one queue to one team leader
A group can be made the manager of an individual call group without giving it the run of the system. That covers the day-to-day: picking up and transferring the calls sitting in that queue, and managing the group itself.
It used to stop at one place. Adding or removing dynamic members, the people who log in and out of a queue rather than belonging to it, was admin-only work, so a team leader could run their queue but not put somebody into it for the afternoon. A separate Manage Call Group permission now covers that, granted per call group rather than across the system: the team leader is nominated as manager of their own queue and gets no say over anyone else's. Setting it up is ours, so tell us which queue and who should run it.
Why a colleague sees something you do not
They are in a different group. Screens outside your group are not greyed out, they are absent, which makes it look like the option was removed rather than restricted.
On current systems the groups can be compared side by side in a permissions table, with a plus or minus per permission and a marker where a group differs from the standard. That settles the question faster than comparing two people's screens.
How permissions combine
A group can inherit from one other group, one level deep. Where the two disagree, a restriction wins over a permission. If the parent group allows something and the child forbids it, the answer is no.
Who can change it
Editing what an existing group may do is open to any administrator. Creating or deleting a group, and setting up inheritance, is reserved for the root administrator. Plan a restructure around someone who does have that account.
Where several systems are joined in a WMS network, the groups are shared across all of them, so a change is not local to one site.
Changing what someone can reach
Moving a colleague between groups, or changing what a group is allowed to do, is something we arrange. Send us a request saying who needs access to what, and why.
Comments
0 comments
Article is closed for comments.