> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/support-resources/faqs/general-faqs.md).

# Generic FAQs

Use this section to view the common questions about the basic capabilities and usage of Avo Assure. It includes queries about common doubts related to the platform, its core functionality, and general usage.

* **Can Avo Assure automate testing for multiple technologies?**\
  **Ans**: Yes. Avo Assure supports automation across various technologies such as web applications, APIs, Desktop Applications, Databases, Mainframe and MS Dynamics 365.
* **Can multiple users work on the same project in Avo Assure?**

  **Ans**: Yes. Users can collaborate on the same project based on their assigned roles and permissions.
* **Can Avo Assure integrate with other tools in the testing lifecycle?**

  **Ans**: Yes. Avo Assure supports integrations with various tools used in the testing lifecycle, such as CI/CD tools and test management systems. For example: Jenkins, Docker, Harness and Azure DevOps.


---

# 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.avoautomation.com/avo-assure/support-resources/faqs/general-faqs.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.