> 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/release7.2/administration/security/connector.md).

# Connector

OvalEdge connectors connect to source systems for metadata crawling and data profiling tasks. After establishing a connector (saving, validating, or crawling), the Security & Governance Admin (SGA) assigned during creation can view all connectors in the "Connectors Security" tab.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXfW1RUDE4WK3lgBevuRVNU31Bp0tA6mGn9Q57sJY8uF8Q8EEV2JGiX8rPztQjDcMkWNmTstquUrel0zOcI7BttvGQ8oCYc7i2HNKUmoRBd2XcK_dgO-ZqFBoXxy2lnULhFW8MO_tQ?key=HQ3_DdDr7Hskac9eJBoI-Xdv" alt=""><figcaption></figcaption></figure>

**SGA Permissions:** The SGA role has the highest permissions by default (Metadata Read-Write & Data Write) for any connector they manage.

**OE\_ADMIN Permissions:** The OE\_ADMIN role has pre-applied Metadata Read-Write & Data Write permissions for all connectors.

**Integration Admin:** The Integration Admin role (defined during connector creation) can edit connector details and perform actions like crawling, profiling, scheduling crawls, and deleting connectors.

**Connectors Permissions and Governance**

The "Connectors Security" allows SGA and OE\_ADMIN roles to manage permissions and governance roles for connectors.

* Add/Modify/Delete Permissions (Individual): Assign or adjust metadata and data access for specific roles or users on a connector.
* Add/Modify/Delete Permissions (Bulk): Manage metadata and data access for multiple roles or users on multiple connectors simultaneously.
* Define Role Access: Set metadata and data permissions for a specific role based on the license type.
* Define User Access: Set metadata and data permissions for a specific user based on the license type.
* Cascade Permissions: Inherit connector-level permissions for all data objects within the connector.
* Define Admin: Assign a role as SGA for a connector, granting them the highest permissions, which are Metadata Read-Write and Data Write.

**Governance Roles**

* Define Governance Roles: Specify mandatory governance roles during connector setup.
* Update Governance Roles (Individual/Bulk): Modify governance roles for single or multiple connectors.
* Cascade Governance Roles: Apply governance roles to all data objects within the connector (optional).
* Delete Role Access: Remove permission assignments for roles on individual or multiple connectors.


---

# 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/release7.2/administration/security/connector.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.
