General concepts

A rule controls what a group of users can do in a channel. It can either allow or deny the following activities:

• To enter and view a channel

  • Not set: A user can see the channel in a client application and is able to switch to it.
  • Allow: A user can see the channel in a client application and is able to switch to it.
  • Deny: A user does not see the channel and cannot access it by any means (neither interactively nor programmatically).
    Important: A user will not receive emergencies from the denied channel.

• To listen to a channel

  • Not set: A user can hear what others are speaking in the channel.
  • Allow: A user can hear what others are speaking in the channel.
    Important: This permission does not guarantee the ability to speak in the channel.
  • Deny: A user does not hear channel's participants.

• To speak in a channel

  • Not set: A user can speak in the channel.
  • Allow: A user can speak in the channel.
    Important: This permission does not guarantee the ability to hear channel's participants.
  • Deny: A user cannot speak in the channel.

• To move another user to a channel (only affects T.Rodon):

  • Not set: A user can add other users to a channel.
  • Allow: A user can add other users to a channel.
  • Deny: A user cannot add others to a channel.

You can combine several privileges within a single rule. For example, to make a team of "observers": allow users to enter and listen for a channel, but deny the ability to speak and add members.

Scheduling

The rules can be time-bound. For example, you can grant access to certain channels according to scheduled work shifts or temporary deny access from private devices during non-working hours.