> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/set-up-a-connection.md).
# Set Up a Connection
1. Log in to the application.
2. Navigate to Administration > Connectors.
3. Click on the + (New Connector) icon.
4. The Add Connector pop-up window is displayed, where users can search for the required connector.
5. The Add Connector window displays the connector-specific configuration fields required to establish a connection. Users can save the connector as a Draft without completing all mandatory fields and continue the configuration later. To establish and validate the connection, complete all mandatory fields marked with an asterisk (\*).
{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}
## Connector Validation
1. Enter all connection details and perform these actions:
1. Click **Validate** to verify the connection.
2. Click **Save** to store the connection for future use.
3. Click **Save** & **Configure** to validate and apply additional settings, then save.
2. Validate Connector using the **nine-dots menu.**
1. Go to the connector screen.
2. Select the connector.
3. Click on the **nine-dots icon**.
4. Select the "Validate Connector" option from the menu.
3. Once the connection is validated and saved, it will be displayed on the Connectors home page.
{% hint style="info" %}
Users can either save the connection details first or validate the connection first and then save it.
{% endhint %}
***
Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA
---
# 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.ovaledge.com/connectors/introduction-to-connectors/setup-and-connectivity/set-up-a-connection.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.