LinkyPermissions, explained
Linky needs permission to replace a shared message safely. The invite requests seven bot permissions; it does not request Administrator.
| Permission | Purpose |
|---|---|
| View Channel | Receive supported messages where Linky has access. |
| Read Message History | Re-fetch the original before deleting it. |
| Send Messages | Send the replacement in a channel. |
| Send Messages in Threads | Send replacements in accessible threads. |
| Embed Links | Display previews and translated cards. |
| Attach Files | Copy attachments and include long translation files. |
| Manage Messages | Delete the original after replacement checks pass. |
Who can enable Linky
The person running /setup needs Manage Server. That is a permission for the administrator, separate from the bot's permissions. Commands reply privately.
Choose the channels
Channel and category overrides determine what Linky can actually see and do. Enabling the server includes every accessible channel and thread, including new ones. Deny View Channel to keep it out of particular channels.
A permission granted on the bot's server role can still be denied by a channel override. Check effective permissions in the affected channel, including @everyone and the Linky role.
Message Content Intent
The bot needs Discord's Message Content Intent to find supported links in ordinary messages. It does not need Server Members Intent. Self-hosted instances must enable Message Content Intent in their own Discord application.