> 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/actions-performed-during-set-up.md). # Actions performed during SuperOffice integration setup When you integrate eMarketeer with SuperOffice, several items are added to SuperOffice automatically so eMarketeer features show up in the client. On SuperOffice 7.3 and newer, these actions run automatically. On older versions, they need to be performed manually. The following items are added: * Web panels * Fields * Types * Sources * Projects ## Database fields eMarketeer creates new database fields in SuperOffice to enrich sales and activities generated by eMarketeer with additional information. The created fields are found in SuperOffice Admin in the "Fields" section under the "Sales" and "Follow-up" tabs. Two fields called "eMarketeer:1" and "eMarketeer:2" are created under "Sales" and "Follow-up" (4 fields in total). All fields are created as "long text" with a length of 195. ## Web panels These items are found in SuperOffice Admin under "Lists" → "Items" tab → "GUI Web panel". The panels load information from eMarketeer. * eMarketeer Lead Board * eMarketeer Automation Queue * eMarketeer Contact Summary * eMarketeer Company Summary * eMarketeer sales info * eMarketeer follow-up info ## Follow-up types These types are created to be used for activities generated by eMarketeer: * Web visit feed * Email feed * SMS/Text feed * Form feed * Landing page feed ## Sale source A new sale source is created called "eMarketeer". ## Troubleshooting Once the fields and panels are created they may not work instantly. To make sure everything works: * Flush SuperOffice so the panels show in the clients immediately. * Make sure the created fields are in a published state. ## Uninstalling eMarketeer eMarketeer does not remove panels or fields when you disable the integration. You need to remove them manually. --- # 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/actions-performed-during-set-up.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.