> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/integrations/automation-anywhere/aari-extensions-enterprise-it-setup-guide/point-pixiebrix-extension-to-staging-authconfig-app.md).
# Point PixieBrix Extension to Staging AuthConfig App
{% hint style="warning" %}
This page is intended for diagnostic and testing use only. Do not use these instructions unless instructed to by support staff.
{% endhint %}
Step by step directions for connecting your AARI account to an Automation Anywhere Control using the Staging AuthConfig App.
* Ensure you’re not logged in to the [PixieBrix Extension](https://app.pixiebrix.com/).
* Navigate to Extension Settings page and set **Authentication Method** to `partner-oauth2`.
* Navigate to the Extension Options page to login. You should see the following screen.
* Add the `env=staging` URL parameter. You should see the following screen. If the default values are not populated, refresh the page.
* Fill out the form appropriately and click **Connect AARI**.
* In a new screen, you will be prompted to login with your IDP (identity provider). In this case, we’re using JumpCloud so we see a JumpCloud login form. Fill out the form appropriately and submit.
* If your login credentials are correct, you will be successfully logged in to the Extension.
---
# 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.pixiebrix.com/integrations/automation-anywhere/aari-extensions-enterprise-it-setup-guide/point-pixiebrix-extension-to-staging-authconfig-app.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.
