> 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/program-guide/bug-bounty-dashboard/settings.md).

# Settings

The Settings page in BugBase allows program managers to manage various integrations and members.

1. **Integration**: In this section, program managers can connect their program with different tools such as Jira, Asana, Trello, etc. to integrate their bug bounty program with their existing workflows and processes. This allows for easy tracking and management of vulnerabilities that need to be fixed. Additionally, program managers can also add new integration or disconnect an existing one.
2. **Members**: In this section, program managers can see a list of all members that are part of the program and the reports that are assigned to them. It allows program managers to keep track of which members are handling which reports and make sure that the workload is distributed evenly among the team. They can also add new members or remove existing members as needed. This section also allows program managers to filter the members based on their roles and reports assigned to them.

{% content-ref url="/pages/qDuxxeDmbW8I2uNZAjY6" %}
[Integrations](/integrations/supported-integrations.md)
{% endcontent-ref %}


---

# 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/program-guide/bug-bounty-dashboard/settings.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.