> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/superoffice/on-premise/on-premise-enabling-the-integration.md).

# On premise: enabling the integration

The final step of the on-premise integration: enter your NetServer details in eMarketeer and start the connection.

This is the final step of the SuperOffice on-premise integration. Your NetServer must already be reachable from eMarketeer and you need a SuperOffice user dedicated to the integration.

If you have not completed these prerequisites, [follow these instructions](https://support.emarketeer.com/integrations/superoffice/on-premise/on-premise-netserver-url-and-user-creation.md).

## Enable the integration

Once SuperOffice is ready, complete the rest of the setup in eMarketeer.

1. Sign in to eMarketeer, click the gear icon at the top right, and choose **Account Settings**.
2. Open **Integrations** in the left-hand Account Settings menu, then click **Manage** on the **Superoffice CRM** card.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-0eda7311bb75c39068ce8db2bce92416d8f94fa4%2Fon-premise-enabling-the-integration-on-premise-settings.png?alt=media" alt="SuperOffice settings with On Premise selected and the Web Service Settings fields"></div>

3. Select **On Premise**.
4. Under **Web Service Settings**, fill in the **User ID** and **Password** of the integration user, and a **WSDL Base URL** pointing to your NetServer SVC-file directory.
5. Click **Apply Changes** to start the integration.

During the integration process, eMarketeer installs items in your SuperOffice instance. [Read more about those actions](https://support.emarketeer.com/integrations/superoffice/actions-performed-during-set-up.md).

When the integration completes successfully, both systems are ready to use.


---

# 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://support.emarketeer.com/integrations/superoffice/on-premise/on-premise-enabling-the-integration.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.
