> For the complete documentation index, see [llms.txt](https://fraudify.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fraudify.gitbook.io/docs/faq.md).

# FAQ

## Why did Fraudify fail to delete an unverified link?

Confirm all of the following:

* Fraudify has Manage Messages permission in the target channel.
* Message Content Intent is enabled in the Discord Developer Portal.
* The sender is not a Discord Administrator.
* The sender is not registered in `server_admins`.
* A channel override is not blocking the bot's permissions.

## How are official server links registered?

Administrators add approved URLs to `server_whitelisted_links` through the database or the administrative tools in `manage.py`.

Official directory resources are stored in `server_resources`.

## Does Fraudify scan direct messages automatically?

Fraudify 1.0 does not perform automatic background scanning of direct messages.

DM auditing is initiated by the user through:

**Apps → Analyze Message**

Automated background DM protection is planned for Fraudify 2.0.

## What happens when an impersonator joins?

The `on_member_join` event triggers `check_and_enforce_impersonation()`.

When the account exceeds the configured similarity threshold, Fraudify bans it and logs the incident.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://fraudify.gitbook.io/docs/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.