Skip to content

Latest commit

 

History

History
23 lines (18 loc) · 2.59 KB

Thread Permissions.md

File metadata and controls

23 lines (18 loc) · 2.59 KB

Thread Permissions

If deployed in a single-server setup you must ensure that threads are created in a Category that only allows visibility to your staff.

The below settings can be used in two-server setups as well.

  1. Set inboxServerPermission to the ID of a role you give the people you want able to run ModMailBot commands. For example, if you have some moderators that all have a "Moderator" role, get the ID of that role and set inboxServerPermission to it.
    Example: inboxServerPermission = 12345

    You can also set it to the name of a role ability if you don't want to create a bespoke role. For example, if you want only people who have the ability to remove messages in your Discord server to issue commands to your bot, set it appropriately.
    Example: inboxServerPermission = manageMessages

  2. Create a Category in your server.

  3. Set the permissions on that category such that only your staff can see the channels. This is the same as setting permissions on channels, except in the Category. You can use the role you created in step #1.

  4. Create your Log Channel there in that category ( logChannelId ).
    Example: logChannelId = 12345

  5. (optional) Create your Attachments channel ( attachmentStorageChannelId ) in that category too, if you choose to use attachmentStorage = discord
    Example: attachmentStorageChannelId = 12345

  6. Set categoryAutomation.newThread to the ID of that category.
    Example: categoryAutomation.newThread = 12345

  7. (optional) Consider setting anonymizeChannelName = on.

    Modified Discord clients can be configured to show channels and categories that the user shouldn't be able to see. Using this method a user could see who is opening threads with your Modmail. This is limited soley to the name of the channel/category and it's description; the contents of the channel are still private.

  8. If your bot is currently running, restart it.