> 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/troubleshooting-so-setup.md).

# SuperOffice Integration Setup Troubleshooting

Common failures when setting up the SuperOffice integration, and how to resolve them.

## When the integration fails to finish

* **The SuperOffice user used for the integration does not have a "Sales" or "Complete" license, or access to this module.** A "Sales" or "Complete" version of SuperOffice is required for the integration.
* **The integration fails with an error related to panels.** Log in to SuperOffice admin and check the web panels. Make sure you do not have "deleted" panels with the same URL as the ones eMarketeer is trying to create. When you delete a web panel in SuperOffice, it is not actually deleted, only hidden. Click the checkbox to show deleted panels. If you find duplicates, edit them to use non-eMarketeer URLs and change the panel name. Then run the integration again.
* **Fields and panels created by the integration may not work instantly.** To make sure everything works:
  * Flush SuperOffice so the panels show in the clients immediately. See the instructions below.
  * Make sure the created fields are published and available for the user groups you want.

## Flush the cache in SuperOffice

If you expect to see changes in SuperOffice, such as new web panels, and they do not appear, you may need to flush the cache.

To flush the cache from your web browser:

1. Log in to SuperOffice CRM in your web browser.
2. In the URL, remove everything after the `?` and type `flush`. Then press Return.

Example: `https://online.superoffice.com/custXXXX/default.aspx?flush`


---

# 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/troubleshooting-so-setup.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.