A critical bug has been identified that may cause document content to be overwritten when editing. As a precaution, we have temporarily unpublished the download for SuperOffice 11.6 . If you have already downloaded version 11.6, please do not install it on any customer production environment . We are working on a corrected version and will release an updated build as soon as possible. We apologize for the inconvenience, and thank you for your patience while we resolve this issue.

Hi, We would like our customers to be able to enter a zipcode in the pre-chat form. Is there a way to add fields in that form?

Release Postponed: Unfortunately, the release of SuperOffice 11.6 On Site has been postponed again. We are currently investigating four critical issues that must be resolved to ensure a positive experience for our On Site customers. Given the high cost of upgrading On Site solutions, we are committed to maintaining a higher standard of quality. Current Timeline: Best-case scenario: Release during next week (Week 50, 2025) Estimated release date: 11 December 2025 Worst-case scenario: Release may be pushed to January Please note that these dates are subject to change as we continue our work across multiple teams. Impact: We recognize this delay may disrupt planned customer activities. However, delivering a stable version is our top priority, rather than releasing a version that would require immediate patching. Important Change – Active Directory Support: No AD Authentication: Version 11.6 On Site will be released without support for Microsoft Active Directory (AD) as an authentication provider . Reason: Microsoft AD is now considered an obsolete technology, making development, debugging, and testing increasingly costly and time-consuming. For Customers Using AD: If you rely on AD authentication, please wait to upgrade until a future release restores this functionality. At this time, we do not have a confirmed date for AD support in upcoming releases.

Hi, I have developed an API integration with SuperOffice in the developer portal (tenant Cust55171) at the endpoint https://sod3.superoffice.com/Cust55171/api/. Everything works correctly against this tenant. Now, I want to connect the same API to the superoficce account I've actually been using the past years (Cust15673) at https://online4.superoffice.com/Cust15673/api/ so that I can access the real data. This account is at https://online4.superoffice.com/Cust15673/default.aspx?browser.extapp0. My question is: How do I register my integration/app so that when i make API calls to for example documents, I get the documents from the Cust15673 account? Thank you in advance.

Hi, Are there any plans to make template variables available for extra fields so they can be used in documents? Right now, we have to duplicate fields to UDEFS just so we can use them in documents.