> 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/connectors/introduction-to-connectors/security.md).
# Security
Security controls restrict access to metadata by default once a connector is created and metadata is crawled. SGAs assign object-level permissions to users and roles explicitly, ensuring roles do not gain automatic access. Permissions apply to each metadata object, including schemas, tables, and columns, maintaining strict alignment with governance policies. This model enforces enterprise-grade security through granular, role-based authorizations, preventing unauthorized access and controlling data visibility precisely.
## Define and Maintain Security on Connector
* Access to metadata is restricted by default after connector creation and crawling.
* SGAs assign permissions to users and roles at the object level
* Permissions cover schemas, tables, columns, and other metadata assets
* Roles gain access only through explicit permission assignment
* The model enforces enterprise-grade security with granular role-based controls
* The model supports enterprise-grade security by controlling access at a granular level through role-based authorizations.
***
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/release7.2/connectors/introduction-to-connectors/security.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.