> For the complete documentation index, see [llms.txt](https://docs.hackenproof.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackenproof.com/dashboard/company-dashboard/manage-bb-program.md).

# Manage programs

You have created a program - great! Now, let’s dive into what statuses it has, and what activities may be required from your side.

You can create the following types of programs:

* Bug Bounty programs (Public or Private)
* Contest programs (Time-limited audit)

Your programs may have the following statuses:

* **Draft.** You just enter the required data and save the introduced changes. You are free to move to the next stage. At this stage, you may need extra help from us with the program draft, or you want to sign legal docs - welcome to [book the call](https://calendly.com/eleonora_hackenproof/30min) or [write us in telegram](https://t.me/Eleonora_HackenProof).
* **In review** by the HackenProof team. After you publish the program, our team will verify it, and you’ll get the approval. In case you have missed providing important details, our team will instruct you on what info should be added.
* **Published**. After signing the agreement and paying a deposit for the program. Published programs are visible to our community of researchers, in case you have chosen a public bug bounty program. In the case of Private Programs, you can start inviting your hackers or ask HackenProof to invite hackers that fit your needs.
* **Archived**. (in case you don’t need the program, you can decide to archive it). All data is saved, and you can reactivate this program at a later time.

You can see the status of your programs in the programs list in your dashboard:

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


---

# 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.hackenproof.com/dashboard/company-dashboard/manage-bb-program.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.