> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c168/q574.md). # Can I request new features or a custom version of the app? Sure thing! [Send us a note](/manual/faq/c169/q575.md). We are always interested in understanding the problems faced in the workplace. Tell us a little more about what feature or enhancement you are looking for, how it would help you at work, and why it is important to you. We take user feedback into consideration when we set the roadmap for our new releases. However, we can't give you any details on when and what new features will be implemented at this stage. ## Related * [FAQ: I prefer the previous version of the app. What next?](/manual/faq/c160/c161/q581.md) * [FAQ: What are the differences between the team and individual offline version of the app?](/manual/faq/c142/c143/q390.md) * [FAQ: What are the differences between the cloud and team version of the app?](/manual/faq/c142/c143/q389.md) * [FAQ: Do you provide development services for customized applications or features?](/manual/faq/c168/q573.md) * [FAQ: Can I set up a call or video conference with support?](/manual/faq/c169/q577.md) --- # 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.reportandrun.com/manual/faq/c168/q574.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.