> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/store/store-faqs-and-troubleshooting.md).

# Store: FAQs & Troubleshooting

Answers to common Store questions, and fixes for listings you can't find.

This page answers common questions about the Store and its agents and apps. Use the troubleshooting entries when you can't find a listing.

## FAQs

<details>

<summary>Who can use the Store?</summary>

Every standard role has **View the store**. See [Roles](/ai-workbench-qore/control-center/admin/roles.md).

</details>

<details>

<summary>Are Store solutions available in every project?</summary>

Yes. Store solutions are tenant-scoped: they're available across every project and account in your tenant. A design system, by contrast, applies to one project. See [Store](/ai-workbench-qore/console/store.md).

</details>

<details>

<summary>How do I start using a Store agent or app?</summary>

On an agent's card, select **Chat Now** to start a conversation. On an app's card, select **Launch** to open the app. Select the card first to review its detail panel. See [Browse agents and apps](/ai-workbench-qore/console/store/browse-agents-and-apps.md).

</details>

<details>

<summary>What does the detail panel show?</summary>

**Overview**, **How it works**, **What you get**, and **Why it matters**, in one continuous view, ending with **Last updated**. See [Review card details](/ai-workbench-qore/console/store/browse-agents-and-apps.md#review-card-details).

</details>

<details>

<summary>Why does an app have no accuracy percentage?</summary>

Only agent cards show an accuracy percentage. App cards show category tags, a short description, and **Launch**. See [Choose a solution type](/ai-workbench-qore/console/store/browse-agents-and-apps.md#choose-a-solution-type).

</details>

## Troubleshooting

<details>

<summary>I can't find a solution in the Store</summary>

Check the tab: agents and apps are listed on separate **Agents** and **Apps** tabs. Then search with **Search store**. See [Find and launch a solution](/ai-workbench-qore/console/store.md#find-and-launch-a-solution).

</details>

<details>

<summary>A listing in the Store catalog isn't in the Store</summary>

The catalog is a snapshot. Agents and apps can be added, removed, or retagged, so the Store itself is the current source. See [Store catalog](/ai-workbench-qore/console/store/store-catalog.md).

</details>

### Related

* [Store](/ai-workbench-qore/console/store.md), [Browse agents and apps](/ai-workbench-qore/console/store/browse-agents-and-apps.md), and [Store catalog](/ai-workbench-qore/console/store/store-catalog.md)

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://1326225582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0qmgQjJ5aArDTj2ACFHG%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/ai-workbench-qore/console/store/store-faqs-and-troubleshooting.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.