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

# Administration

- [Product](https://docs.qatts.com/administration/product.md): Our product is that which we are going to perform automated software testing on
- [How to Add Product](https://docs.qatts.com/administration/product/how-to-add-product.md): Step by step walkthrough of how to add a product
- [Configure Test Data Repository](https://docs.qatts.com/administration/product/configure-test-data-repository.md): Test data is a set of data that are used in the software testing
- [Code Branch](https://docs.qatts.com/administration/code-branch.md): Code Branch -  That which maintains the version of your Product on which you are going to automate
- [How to Add Code Branch](https://docs.qatts.com/administration/code-branch/how-to-add-code-branch.md): Step by step walkthrough of how to add code branch
- [Feature](https://docs.qatts.com/administration/feature.md): Learn everything there is to the features page
- [Client](https://docs.qatts.com/administration/clients.md): Different clients are created based on different datasets
- [How to Add Client](https://docs.qatts.com/administration/clients/how-to-add-clients.md): Step by step walkthrough on how to add a client
- [Deployment](https://docs.qatts.com/administration/deployment.md): Deployment holds all the target environment details of your product
- [How to Add Deployment](https://docs.qatts.com/administration/deployment/how-to-add-deployment.md): Step by step walkthrough of how to add deployment
- [Database Config](https://docs.qatts.com/administration/deployment/database-config.md)
- [Email Config](https://docs.qatts.com/administration/deployment/email-config.md): Any email account that need to be used must be configured at deployment. Each mail box configuration as grouped as alias. So all the properties must have alias name in the prop name. With the help of
- [Node](https://docs.qatts.com/administration/node.md): A Node is a runtime environment for test execution.
- [Streaming Configuration](https://docs.qatts.com/administration/node/streaming-configuration.md): Once you have registered your node in QATTS, We just need to follow a few simple steps to get executions streamed. QATTS streaming works on the windows platform, when the agent-service is running.
- [How to register node for streaming](https://docs.qatts.com/administration/node/how-to-register-node-for-streaming.md): The guacamole server provide an easy way of registering, testing the nodes and disconnecting the
- [Status And Actions](https://docs.qatts.com/administration/node/status-and-actions.md): This page describes various options in the node with their working and configurations
- [Agent](https://docs.qatts.com/administration/agent.md): Agent might be a browser or mobile device
- [User](https://docs.qatts.com/administration/user.md): A step by step guide to creating a user
- [Role](https://docs.qatts.com/administration/role.md): A Role specifies what type of access can a user have in QATTS.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qatts.com/administration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
