> For the complete documentation index, see [llms.txt](https://docs.bifrost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bifrost.io/for-the-community/governance/opengov-tracks/whitelistedcaller.md).
# WhitelistedCaller
## **What to post in the** WhitelistedCaller **Track?**
The WhitelistedCaller Track has same access with the root track, but it can be whitelisted by fellowship for acclerating. Hence, it is normally used for emergency requirements.
Check passed WhitelistedCaller Track proposals:
* Bifrost Polkadot: [Bifrost Polkadot ](https://bifrost.subsquare.io/referenda/tracks/1)
* Bifrost Kusama: [Bifrost Kusama](https://bifrost-kusama.subsquare.io/referenda/tracks/1)
## **Guidance for** WhitelistedCaller **Proposing**
1. Contact Bifrost core contributors to discuss and validate the issue that should be involved in Whitelist.
2. Post the discussion in subsquare to clarify the details of the issue.
3. Check [WhitelistedCaller Track parameters](/for-the-community/governance/opengov-tracks.md#whitelistedcaller), submit the preimage then contact with Bifrost team, the fellowship member needs to whitelist the preimage in fellowship whitelisted proposal.
The WhitelistedCaller Proposal Construction:
1. Add preimage under whitelist: dispatch\_whitelisted\_call\_with\_preimage.
2. Use that preimage to submit the whitelisted proposal.
---
# 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://docs.bifrost.io/for-the-community/governance/opengov-tracks/whitelistedcaller.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.
