> For the complete documentation index, see [llms.txt](https://docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbase.ai/bounty-hunter-guide/programs-directory/whitelist.md).

# Whitelist

## Requesting Whitelisting for Assets

To request whitelisting for assets requiring authorisation, follow these steps:

1. **Navigate to Program Page**
2. **Access the Credentials & VPN Tab**: Select the **Credentials & VPN** tab.
3. **Locate the Whitelist Section**: Scroll down to the **Whitelist** section to view assets requiring whitelisting.
4. **Request Whitelisting**:
   * Individually request whitelisting for each asset.
   * A prompt will display the specific requirements, indicating whether phone, email, or both are needed.

<figure><img src="/files/sRd1B1viSPyeRuLKVctt" alt=""><figcaption></figcaption></figure>

**Additional Notes**:

* If a phone number is required, ensure it is set up in the **User Settings** page before requesting whitelisting.
* For email requirements, the default BugBase alias will be used: **{username}@teambugbase.com**
* Requirements may vary by asset.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bugbase.ai/bounty-hunter-guide/programs-directory/whitelist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.