> For the complete documentation index, see [llms.txt](https://docs.allganize.ai/alli-llm-app-market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allganize.ai/alli-llm-app-market/manual/for_user.md).
# Alli Works
アプリ管理へ追加されたアプリをユーザーが確認できる画面です。ユーザーはこの画面からアプリを選択し、利用します。
デフォルトのAIエージェントや、管理者によりアプリ管理へ追加されたアプリをユーザーが確認できる画面です。ユーザーはこの画面からアプリを選択し、利用します。
Alli Worksを表示するには[アプリ管理](https://docs.allganize.ai/alli-llm-app-market/manual/app-management)を開き、右側にある「Alli Works」を押下することで、上記の画面が表示できます。Alli Worksをユーザーへ展開する場合、Alli WorksへのアクセスURLを配布します。\
Alli WorksへのアクセスURLはプロジェクト設定 ＞ Alli Works設定 ＞ Alli WorksのURLをコピーください。
### Alli Worksの名称変更
Alli Worksの名称は自由に変更が可能です。
ダッシュボードのプロジェクト設定からAlli Works設定を選択し、企業名を変更後にページ下部にある適用ボタンを押下するとアプリランチャーへ反映されます。
変更を実施した場合、プロジェクト単位で名称が変更となります。詳細に関しては[こちら](/alli-llm-app-market/manual/project-settings/alli-works-setting.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.allganize.ai/alli-llm-app-market/manual/for_user.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.
