Event log

The event log posts a short message in a channel of your choice each time something happens: a ticket opens or closes, someone is added, a setting changes, or Sortr runs into a problem. You choose which of the 37 events are posted. Two of them are always on.

Dashboard › your server › a panel › Transcripts/Logging › Event log

#Choose a log channel

1. Open the panel. In the dashboard, pick your server, then the panel.
2. Go to Transcripts/Logging, then Event log. Transcripts/Logging is in the left menu under Afterwards.
3. Pick the channel. Under Log channel, choose where posts go. Only channels Sortr can post in are listed.
4. Tick the events. Under Events, tick the ones you want. All and None set every event at once, and each group has its own Select all or Clear. Click an event's name to see an example beside the list.
5. Save. Press Save changes.

Each panel has its own log channel and its own choice of events, and a ticket is logged by the panel it was opened with. For one log covering the whole server, pick the same channel on every panel. A panel made with Create a new panel from an option starts with the log channel of the panel you made it from. To stop posting, clear the channel with the × beside its name.

A ticket Sortr took over from Ticket Tool is logged by the panel it was filed under, but only posted in that panel's log channel if nobody outside the roles that could see the ticket can read that channel (the server owner, Administrators and bots aside), both when it was taken over and when each entry is posted. Otherwise its entries are recorded but not posted, so a ticket only some roles could see is never written up where the others read.

#What Sortr needs in the channel

Sortr needs View Channel, Send Messages and Embed Links in the log channel, plus Attach Files if your transcripts are posted there too. A private staff channel has to let Sortr's role in with them, in the channel's own permissions (see Private categories and channels). If Sortr cannot post, it skips the post rather than trying again and again, and the event is still recorded (see below). Saving the panel makes Sortr try a channel it had given up on straight away.

The screen tells you when posts cannot go out:

• No channel picked. It says "No channel picked, so nothing is posted. Sortr still records the events ticked below and keeps them for 90 days."
• The channel was deleted. The field shows "(deleted channel)" and the screen says "The log channel no longer exists, so nothing is posted. Pick another."
• Sortr can't see the channel. When the channel is private and Sortr's role is not let in, the field shows "(Sortr can't see it)" and the screen says "Sortr can't see the log channel, so nothing is posted. Let Sortr's role in with View channel, Send messages and Embed links, or pick another."
• Sortr can no longer post there. A saved channel Sortr can see but no longer post in shows as "#staff-logs (Sortr cannot post here)", with "Sortr can no longer post in #staff-logs, so nothing is posted there. Give Sortr View channel, Send messages and Embed links in it, or pick another."

#Every event

The events come in the same groups as on the screen. "On" means ticked for a new panel. "Always" means the event cannot be switched off: the screen shows it ticked, with a lock, and All, None and Clear leave it alone.

#Ticket events

Transcripts explains when a delete saves a transcript.

#People in tickets

#Messages in tickets

These only cover ticket channels, never the rest of your server. Deleted and edited messages from bots are not logged. Each member's edits are logged at most 5 a minute, and their deleted messages at most 5 a minute; any more in that minute are neither posted nor recorded, so one member cannot flood the log channel.

#Transcripts

#Refused opens

A member refused again and again for the same reason is logged once every 10 minutes, so pressing a button on repeat makes one entry. A refusal because an option is not for the member's role is logged by the panel the option is on. The rules are set under Limits and rules, and who can use an option under Buttons.

#Configuration changes

Commands registered or removed is made only when a command is added to the server or removed from it. Switching a command on in a panel while another panel already has it on adds nothing to the server, and changing the roles under a command's Who can use it changes who can use it and who Discord lists it for, not which commands exist, so neither makes that entry. Both are in the panel's Settings changed entry instead. Slash commands explains the roles.

A save cannot hide itself. Its Settings changed, Staff permissions changed and Bot message edited entries are logged when the event was ticked before the save or after it, so switching an event off in the same save still logs that save. When the save moves the log channel, its entries are posted in the old channel and the new one. Integrations changed works the same way, and is always on.

#Sortr health

When something in this group appears, Permissions and Troubleshooting explain the fix.

#When people could not be let in or out

If Discord refuses Sortr in a ticket's channel, for example when its role lacks Manage Permissions there, changing who is in the ticket can fail. Sortr then says so, naming the people involved, and says what to let Sortr's role in with, such as "Sortr needs Manage Permissions on the channel: let Sortr's role in with it, in the channel's or its category's permissions." These come under Missing Discord permission, or under Something went wrong when Discord refused for another reason:

• "Could not lock the ticket owner out" or "Could not lock everyone out of a closed ticket": a close could not take everyone's access away. It names who may still be able to read or write in the ticket.
• "Could not let everyone back into a reopened ticket": a reopen could not give everyone their access back. It names who is still locked out.
• "Could not add a member", "Could not add a role" and "Could not remove a member": /add or /remove could not change the channel. "A member was added with less access" and "A role was added with less access": they were let in without the permissions it names.
• "Support roles not updated on every ticket": a save changed the panel's support roles, and the tickets it names kept their old ones.
• "Sortr cannot make a ticket private": no ticket was opened, because Sortr could not hide it from @everyone or let itself in.
• "Sortr could not pin the opening message" (or, on a ticket taken over from Ticket Tool, "Sortr could not pin a taken-over ticket's message").

Bots in a ticket, Ticket Tool's included, keep their access when it closes. Permissions lists what Sortr needs for each.

#What a Category full entry says

Each entry names the ticket and the panel.

• New tickets. The entry is titled "Every category is full" and says the ticket is being created without a category.
• Closed tickets. The entry is titled "Every closed-ticket category is full" and says the ticket stays where it is. It is only made when Where closed tickets move is set to create categories. Without that, a closed ticket stays where it is and nothing is logged.
• Why no category was created. When the list has Create a new category when these are full switched on, the entry adds a line starting "No new category was created:" with the reason, such as the server being close to Discord's limit of 500 channels.
• Deleted categories. When none of the categories in the list is still in the server, the entry is titled "No category to put the ticket in" for a new ticket, or "No category to move the ticket to" for a closed one, and asks you to pick one.

Destination category explains what happens to the ticket and how to let Sortr create categories.

#Events are recorded even without a channel

Every event you have ticked, and those that are always on, is recorded by Sortr first and posted second. With no log channel, or a channel Sortr cannot post in, the post is lost but the record is kept. Records are deleted after 90 days. The dashboard has no screen for reading them: you see events only in the log channel.

An entry for a ticket taken over from Ticket Tool that may not be posted in the panel's log channel (see above) is recorded the same way.

A record says what happened, when, in which ticket and who did it. The text of deleted or edited messages and the names of deleted files only go into the Discord post, and are never stored. Events you have not ticked are neither posted nor recorded, apart from those that are always on. More in Privacy and data.

#Good to know

• Server-wide events. Rate limited by Discord belongs to the whole server, not one panel. It is posted by the oldest panel that has it ticked and a log channel set. Commands registered or removed is logged in the panel whose save changed the commands. Set the same log channel on every panel to be sure you see both.
• Busy moments. Posts go out in order, one server at a time. If more than 50 are waiting for your server, the extra ones are recorded but not posted. Missing Discord permission, Category full, Panel message gone, Integrations changed and Server almost out of channels are posted all the same.
• Transcripts in the same channel. If your transcripts use Same as the log channel, the transcript posts and the log entries share this channel.