> 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/docs/docs_se/integrationer/superoffice/on-premise/on-premise-enabling-the-integration.md).
# On premise: aktivera integrationen
Det sista steget i on-premise-integrationen: fyll i dina NetServer-uppgifter i eMarketeer och starta anslutningen.
Detta är det sista steget i SuperOffice on-premise-integrationen. Din NetServer måste redan vara åtkomlig från eMarketeer och du behöver en SuperOffice-användare dedikerad till integrationen.
Om du inte har slutfört dessa förutsättningar, [följ dessa instruktioner](/docs/docs_se/integrationer/superoffice/on-premise/on-premise-netserver-url-and-user-creation.md).
## Aktivera integrationen
När SuperOffice är klart slutför du resten av uppsättningen i eMarketeer.
1. Logga in i eMarketeer, klicka på kugghjulsikonen uppe till höger och välj **Account Settings**.
2. Öppna **Integrations** i Account Settings-menyn till vänster och klicka sedan på **Manage** på kortet **Superoffice CRM**.
3. Välj **On Premise**.
4. Under **Web Service Settings** fyller du i **User ID** och **Password** för integrationsanvändaren, och en **WSDL Base URL** som pekar mot katalogen med SVC-filer för din NetServer.
5. Klicka på **Apply Changes** för att starta integrationen.
Under integrationsprocessen installerar eMarketeer objekt i din SuperOffice-instans. [Läs mer om dessa åtgärder](/docs/docs_se/integrationer/superoffice/actions-performed-during-set-up.md).
När integrationen slutförs korrekt är båda systemen redo att användas.
---
# 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/docs/docs_se/integrationer/superoffice/on-premise/on-premise-enabling-the-integration.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.
