> For the complete documentation index, see [llms.txt](https://doc.keepnetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.keepnetlabs.com/next-generation-product/getting-started/6.-setup-phishing-reporter/deploy-keepnets-customisable-phishing-report-button/step-1.-download-phishing-reporter.md).
# Step 1. Configure the Phishing Reporter
#### **Step 1.**
To download the Phishing Reporter, go to the **Phishing Reporter** tab on the left hand side and select **Configure Add-in** (or click on Settings).
Phishing Reporter > Configure Add-in (or Settings) — first step to download.
#### **Step 2.**
On the first settings page, **Add-in Settings**, is where you can customise how the Phishing Reporter appears in your employees inbox including:
* Logo
* Button labels
* Messages users receive when reporting emails
#### **Step 3.**
Your **Email Settings** page is where you select who will be notified about suspicious emails and the email you want them to receive. You can add as many emails as you would like here.
#### **Step 4.**
**Proxy**: If users are accessing the internet through a proxy, you can enable the plugin to detect the proxy configuration of the computer where it will be installed.
**API**: If you require any changes to be made to the API settings, please let our support team know on .
**Enterprise Vault**: When selected, the suspicious email can be searched in the user's backup emails during the investigation. (*Only for MSI phishing reporter add-in*)
#### **Step 5. (Only for MSI add-in)**
The **Diagnostic Tool** provides information about the status of the add-in. For example, if the add-in has been disabled by a user, the **Diagnostic Tool** can be used to ensure automatic activation or make system admins aware.
{% hint style="warning" %}
The Diagnostic Tool is designed only for use on Outlook Desktop add-in with the MSI extension. When the add-in is distributed over Office 365 or Google Workspace, it is automatically installed and active for all users.
{% endhint %}
**✅ You have now customised the Phishing Reporter.**
**Now, go to** [**Deployment**](https://github.com/ucarozan/keepnet-docs/blob/main/next-generation-product/getting-started/6.-setup-phishing-reporter/step-2.-deploy-phishing-reporter) **➡️**
---
# 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://doc.keepnetlabs.com/next-generation-product/getting-started/6.-setup-phishing-reporter/deploy-keepnets-customisable-phishing-report-button/step-1.-download-phishing-reporter.md?ask=&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.
