> 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/configuration-and-management.md). # Configuration & Management The Configuration & Management provides complete control and oversight of connector operations. It supports starting metadata extraction, scheduling recurring jobs automatically, and tracking connector status and health. Administrators can manage connector details and advanced features like delta and recrawl workflows, ensuring data remains current and lineage is accurately maintained. The dedicated subpages allow focused handling of crawling, scheduling, and connector management tasks. **Features**: * Initiate metadata extraction through **Crawl & Profile** actions. * Configure automated schedules using the **Schedule Connector** feature for recurring jobs. * Monitor connector health and status in real-time. * Perform administrative tasks such as editing, renaming, validating, and deleting connectors. * Manage advanced options including delta crawl, recrawl workflows, and lineage building. * Access dedicated subpages for **Crawl & Profile**, **Schedule Connector**, and **Manage Connectors** to handle specific operations. *** 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/configuration-and-management.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.