These permissions must be set server-wide (which should be the case by default, if using the proper invite) and should not be impeded in the channel you want BibleBot to function in.
For command usage, it’s important that you do not prevent users from using commands in the Integrations section of Server Settings.
| Permission | Explanation |
|---|---|
View Channel | The bot can’t see verses in messages without this permission. |
Send Messages | The bot can’t respond to verses or commands without this permission. |
Send Messages in Threads | The bot can’t respond to verses or commands in threads without this permission. |
Add Reactions | The bot will add reactions to paginator commands, such as /search, /listversions, etc., to allow you to change the page. |
Embed Links | This allows the bot to respond with the fancy interface we’ve come to know and love. |
Read Message History | The bot needs this permission in order to edit the response message for each page change in a paginator. |
Manage Messages | After a paginator times out (180 seconds), the bot removes the reactions to indicate that the paginator is no longer active. |
Manage Webhooks | In order to setup and manage automatic daily verses, BibleBot needs to be able to add, edit, and remove the webhook that achieves this. |
Use Application Commands | BibleBot uses slash commands as required by Discord. Without this permission, you will not be able to use commands. |
Use External Emojis | This allows BibleBot to provide some additional flair in responses to /biblebot, /versioninfo, etc. |
Is BibleBot secure? What about privacy?
Rest assured, BibleBot is incredibly secure with a ridiculously small attack vector. The only way BibleBot could ever become compromised is through the obtaining of our authorization token – which we keep sealed tight on our infrastructure. We never write code that could create an opportunity for exploitation and our infrastructure utilizes many security measures to prevent unwanted access (SSH key logins, no root login, SELinux, etc.).
In the incredibly rare chance we become compromised, i.e. through the obtaining of our authorization token – the damage to users should be fairly minimal, provided no additional permissions have been given to the bot. We do NOT encourage you to give the bot Administrator permissions or anything that we do not specify on this page, we are not responsible for the damage that can be caused in an event because you gave the bot too many permissions. In the event it does happen, the two worst things that can happen is the ability to log and delete messages. The Manage Messages and Manage Webhooks permissions are the only permission we have that can remove something. We don’t want to have the Manage Messages permission, but this is the only way we can remove reactions to the paginators.
Otherwise, your privacy is assured, to the fullest extent of the law. BibleBot and the lead software engineer (srp#0001) have been verified by Discord for meeting Discord privacy and data security standards. We strictly follow the Discord Developer Terms of Service and the Discord Developer Policy. BibleBot does not interact in any way to messages that do not trigger the bot (i.e. a command or verse reference). Interactions with the bot are only saved to a temporary file for use in the event of any errors.
We have not requested for any Privileged Intents that Discord provides, with the exception of Message Content. This is to continue providing our normal method of verse referencing, otherwise we would have to place referencing behind a command.