> For the complete documentation index, see [llms.txt](https://docs.empowergpt.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empowergpt.ai/assistants/assistants-overview.md).

# Assistants Overview

**Assistants** in EmpowerGPT allows users to design, configure, and deploy customized AI assistants tailored to specific tasks, workflows, and business needs.&#x20;

Each assistant can be fine-tuned with instructions, capabilities, and model selection to ensure it performs optimally for its intended use case.&#x20;

Users can also **share assistants with colleagues**, enabling team-wide collaboration and consistent task execution.

On the **Assistants** page, all assistants accessible to the user are displayed in a card layout. Each card includes:

* Assistant Name
* Description
* Creator’s Name

Depending on the user’s role and permissions, additional actions (such as edit, duplicate, or delete) appear when hovering over an assistant card.

<figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2F87WBd53qNHQMlzOJN3Fq%2FPage_106.png?alt=media&amp;token=9d30c85b-93f0-4eb8-ba02-e114c4601f84" alt=""><figcaption></figcaption></figure>


---

# 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.empowergpt.ai/assistants/assistants-overview.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.
