> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.7/support/ideas.md).

# Ideas

The Platform9 Ideas portal, accessible [here](https://ideas.platform9.com/) is your direct path to helping define future releases. The ideas portal enables you to create, vote and comment on, not just your own ideas, but ideas from everyone; including the whole team at Platform9. Once you have created an idea the Platform9 product management will review it’s viability and potentially plan it for a future release. Every step along the lifespan of an idea the ideas portal will notify you of comments, state changes and when implemented, that your idea has been shipped in a release!

If you would like to know more about how to submit an idea read the [auto$](https://github.com/platform9/pcd-docs-gitbook/blob/main/kubernetes/ideas-faq/README.md) doc

## Platform9 Ideas Portal

Create and vote for ideas at <https://ideas.platform9.com>

<figure><img src="https://351724846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHSO0ts94Xucvw1aQnUua%2Fuploads%2Fgit-blob-21bcdbeaec0b4997b63f5517a6120a0d05c8313e%2F1605660445.png?alt=media" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/managed-kubernetes/5.7/support/ideas.md?ask=<question>&goal=<user_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.
