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

# Announce Dashworks

Hey everyone,

We’re excited to introduce you to Dashworks, our new AI search assistant. Dashworks connects with our company’s internal knowledge to find answers, search docs, and more.

**What can Dashworks help me with?**

1. **Summarize**: *Tell me about the Phoenix project*
2. **Search**: *Do we have any decks for Fintech industry?*
3. **Answer**: *How can a customer upgrade their plan?*
4. **Create**: *Write a blog post about our upcoming launch in Australia*

Learn about other use cases of Dashworks for your role [here](https://support.dashworks.ai/use-cases/engineering#:~:text=Other%20Sources-,USE%20CASES,-Engineering).

**How** **do I get started?**

1. Sign up at [web.dashworks.ai/signup](https://web.dashworks.ai/signup) with your work email.
2. Connect all the apps you use daily from the [App Store](https://web.dashworks.ai/integrations).
3. Start asking questions from the [homepage](https://web.dashworks.ai/).
4. Optionally, connect Slack to DM Dashworks, or install the Chrome extension to access it from anywhere.

If you have any questions or feature requests, please feel free to contact us or the Dashworks team via the in-app chat.


---

# 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://support.dashworks.ai/admin/announce-dashworks.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.