> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/enabling-an-interface.md).

# Enabling an interface

### Introduction

This procedure describes how to enable an interface. Interfaces when created are disabled by default.

If the interface has been configured to run on a schedule or added to a sequence, it will not run until such time as it has been enabled.

If an interface has been configured to run manually, it cannot be run until such time as it has been enabled.

### Procedure

1. Click **Manage** from the menu bar.
2. Click **Enterprise Data Interface**.

   The Enterprise Data Interfaces list window opens.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4d711cca6d80fa23ccdc392e317348d7fa83b2f5%2Fbookinginterfacemlw.png?alt=media)
3. Select the interface you wish to enable/disable.
4. To enable the interface, click the **Enable** button.

   The interface is enabled and the status is changed to "Manual", "Scheduled" or "Sequenced".

   The **Run Now** button is enabled.
5. To disable the interface, click the **Disable** button.

   The interface is disabled and the status is changed to "Disabled".

   The **Run Now** button is disabled.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/enabling-an-interface.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.
