> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/archive/features-legacy-databutton-web-app-builder/app-preference-features/app-management.md). # App Management ### How to Access Click on your application name in the top left corner of your workspace, then select Settings > App Management ### App Details NAME * The display name of your application {% hint style="info" %} Note: Changing this does NOT change your deployed app's URL {% endhint %} * Used by the agent to understand your app's purpose PITCH * Brief elevator pitch of what your app does * Helps the agent understand core functionality * Example: "Email Thread Summarizer - Automatically summarizes Gmail conversations using AI" APP DESCRIPTION * More detailed explanation of features and capabilities * Include integrations, key workflows, and use cases TARGET AUDIENCE * Who will use this app? * Examples: "Busy professionals", "Sales teams", "Customer support agents" * Helps agent make UX decisions appropriate for your users To Save: Click Apply Changes after updating --- # 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.riff.ai/archive/features-legacy-databutton-web-app-builder/app-preference-features/app-management.md?ask=&goal= ``` `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.