> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/faq/request-a-feature.md). # Request a feature Suggest what akenza should build next, and follow what happens to it. Feature requests are collected on a public board, where every customer can add a request, vote on the ones already there, and follow what is being worked on. {% embed url="" %} ## Writing a request that lands The board is read as input to the product roadmap, so a request is more useful when it describes the problem rather than only the solution you have in mind. What helps: * **The use case.** What you are trying to achieve, and why the current behaviour gets in the way. * **Your workaround.** What you do today instead, including the manual steps or the external tooling it costs you. * **The scale.** How many devices, workspaces, or people are affected, and how often. * **The outcome, not the implementation.** "I need to know when a device stops reporting" leaves room for a better answer than "add a checkbox here". Search the board before adding a request. Voting on an existing entry and adding your use case in a comment carries more weight than a second entry saying the same thing, because it keeps the demand visible in one place. ## What happens next Requests are prioritized against the product strategy and against how often the same need comes up. Not everything can be built, and a request appearing on the board is not a commitment to deliver it, but it is visible to the team and to other customers who may vote on it. The board itself is where the status lives. Follow your request there to see updates and to watch what is planned. {% hint style="info" %} Something broken rather than missing belongs in the [Service Desk](/faq/service-desk.md), where it is tracked as an issue instead of waiting on votes. {% endhint %} --- # 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.akenza.io/faq/request-a-feature.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.