> 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-netserver-url-and-user-creation.md).
# On premise: NetServer URL and user creation
## Requirements
For the integration to work, the following must be true:
* NetServer is installed on your server and reachable from eMarketeer over HTTP (port 80, 8080, or 443).
* The exposed NetServer version is `/services84`.
* A SuperOffice user exists for the integration, and is either a licensed user with a Sales or Complete licence, or an "Other user".
* The SuperOffice REST API allows GET, POST, PATCH, and DELETE operations.
## REST and SOAP API
The integration is built on the SuperOffice REST API. The `/services84` endpoint still needs to be available because it is used for authentication.
## Allowing eMarketeer to access your server
Unless your NetServer is publicly exposed, you need to make sure eMarketeer can reach it. Security measures typically include restricting access by firewall.
### Firewall
All traffic comes from a single eMarketeer server, so you can set firewall rules accordingly.
| IP address | Host name | Ports |
| ------------- | --------- | ------------- |
| 54.155.30.167 | n/a | 80, 8080, 443 |
The IP address does not respond to ping.
## Retrieve the WSDL URL from IIS
eMarketeer needs a URL pointing to the directory where the NetServer web service functions are located. To find it:
1. Open IIS on your server.
2. In the left panel, open the **Sites** tree and locate the site that holds your NetServer.
3. Among the subfolders, find one called **Services84** (the exact name depends on version).
4. The folder contains `.svc` files. Click **Content view** to confirm.
5. Right-click **Contact.svc** and select **Browse** to open it in your browser.
6. The browser shows the complete path to the directory.
The path (excluding the filename) is the WSDL URL to use in eMarketeer.
Example: `https://www.yourcompany.se/SuperOffice/Remote/Services84/`
If the domain in your URL is `localhost`, replace it with the correct public domain name.
Save this URL for the next step.
## Create the integration user
eMarketeer needs to sign in to NetServer as a SuperOffice user. You have two options:
* Create an "Other" user.
* Use a licensed user.
The recommended option is an "Other" user because it does not consume a user licence. Note that "Other" users can only be created from the desktop admin, not the web admin.
To create an "Other" user, open SuperOffice Admin and go to user management. On the **Other** tab, create a new user with a username and password.
You can also use a licensed user. Create a new SuperOffice user (not a Windows user) and set its user level to 0 (zero).
Save the username and password.
## What to do next
With the URL and user credentials ready, you can [enable the integration](/integrations/superoffice/on-premise/on-premise-enabling-the-integration.md).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://support.emarketeer.com/integrations/superoffice/on-premise/on-premise-netserver-url-and-user-creation.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.