R1–R4 roles, moderation and broadcasts

The leader (LEADER) and R4 have the full administrator toolkit: creating and deleting channels, mutes, removing members, announcements, broadcasts and polls. The only difference between them is managing roles.

R3, R2 and R1 can read everything, write in channels, edit and delete their own messages, and leave the alliance. They cannot moderate or create channels.

You can only act on members ranked below you. The leader can act on anyone except themselves; R4 can act on R3, R2 and R1, but not on another R4 or on the leader.

You cannot mute yourself, and you cannot apply a second mute while the previous one is still active.

A mute lasts between 5 minutes and 28 days and requires a reason. Any administrator can lift it.

Both the leader and R4 can change roles, with restrictions. R4 cannot change the role of another R4 or of the leader, and cannot promote anyone to R4 — only the leader can.

Promoting someone to R4 automatically demotes the current R4 to R3, so the alliance always keeps exactly one second-in-command. Promoting to R3, R2 or R1 is available to both the leader and R4.

Only the current leader can transfer leadership, and only to a member whose role is exactly R4. The previous leader becomes R4 and the new leader gets a notification.

The leader cannot leave the alliance until leadership is transferred. This prevents an alliance from being left without a manager.

Authors can edit or delete their own message at any time, as long as it has not been permanently deleted. In direct messages that is the only way to remove text — nobody can delete somebody else's direct message.

In a channel, a message can be deleted by its author or by any administrator.

An announcement is a one-off message for the whole alliance. The leader and R4 can post them, and they stay in the chat as opposed to being transient notifications.

A broadcast notifies every alliance member on a schedule. The leader and R4 can create, edit, disable and delete them.

Frequency is one of three options: every N days, where N runs from 1 to 365; on selected weekdays, Monday through Sunday; or on selected days of the month, 1 to 31. The time is precise to the minute.

Watch out for one behaviour: if the selected day of the month does not exist, the broadcast fires on that month's last day instead. With 29, 30 and 31 selected, February produces three notifications — one on each of the month's final days.

A broadcast is tied to a specific channel and only reaches members of your own alliance.

The scheduled time is evaluated in the server time zone, not your device clock, which is why each card shows a "Next send" line with that same time zone attached — use it rather than your own device time. The "last sent" field, on the other hand, is displayed in your local time.

If the server restarts or is being updated right when a broadcast is due, the notification still arrives: the first healthy tick has 5 minutes to deliver what was missed. Past that window the send for that day is skipped.