> 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/guides.md). # Task Guides Step-by-step guides for every task in Qore, organized by what you want to do. Task guides are organized by what you want to do. Each one opens with a list of tasks, then gives the steps for each, with links to the reference pages for detail. *** ## :hammer: Console Build and run apps and agents in a project.

:user-gear:

Use the Console Operator

Ask, build, schedule, and answer gates from one chat.Use the Console Operator

:robot:

Create an agent

Build, configure, test, export, and manage agents.Create an agent

:diagram-project:

Create a flow

Build, test, and publish automations, and use them from agents.Create a flow

:database:

Create a knowledge base

Add sources, sync files, and test the answers agents get.Create a knowledge

:layer-group:

Create a design system

Set a brand's style, logos, fonts, and colors for apps.Create a design system

:mobile:

Create an app

Build, preview, check, publish, and manage apps.Create an app

:link:

Integrate an agent

Attach an agent to an app you built in Qore, or embed it in an external app.Integrate an agent

:plug:

Connect an integration

Connect a third-party service to your account from Integrations.Connect an integration
*** ## :shield-halved: Control Center Operate and govern apps and agents across the account.

:user-shield:

Use the Governance Operator

Ask about the account, approve staged changes, schedule runs, and answer gates.Use the Governance Operator

:chart-line:

Monitor activity

Trace runs, read analytics, audit changes, inspect logs, and export or report.Monitor activity

:wallet:

Manage costs and limits

Review credit usage and history, set hard limits, and get alerts.Manage costs and limits

:clipboard-check:

Evaluate agent quality

Create evaluators, score live traffic, and review low-confidence results.Evaluate agent quality

:scale-balanced:

Govern agents and models

Stop agents, review connectors, load a governed graph, and configure AI Gateway.Govern agents and models

:user-gear:

Manage users and access

Invite people, set roles, organize teams, manage sign-in, and issue API keys.Manage users and access
To see which roles can do each task, see [Roles and tasks](/ai-workbench-qore/roles-and-tasks.md). For what each screen and setting does, see [Platform Reference](/ai-workbench-qore/platform-reference.md). For answers to common questions, see the [Help Center](/ai-workbench-qore/help.md). *** {% columns %} {% column width="83.33333333333334%" %}

Maintained by Abhishek Paul
AI-assisted, human-approved

{% endcolumn %} {% column width="16.666666666666664%" %}
{% 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/guides.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.