Partner Portal · Guides and support

Partner Portal release notes

Track Partner Portal pre-release changes, deployment packaging, themes, app-only sign-out and documentation. Marketplace availability is pending.

All Partner Portal information

Reviewed · Marketplace release in preparation

Pre-release status

These notes describe the current development build and publishing materials. A production Marketplace version and acquisition link have not been announced. Technical package version numbers will be published with confirmed releases.

8 November 2026 — Product identity and guides

  • Created the Partner Portal product mark and Marketplace logo exports.
  • Added product and portfolio information, captioned walkthrough and customer documentation.
  • Prepared stable support, deployment, administrator/member, privacy and release-note destinations on Smart365.ai. Publication requires deploying the website.

7 November 2026 — Bundled deployment workflow

  • Selected the Marketplace deployment ZIP containing the Linux application ZIP and manifest.
  • Native OneDeploy installs into persistent customer App Service package storage; no publisher-controlled static application ZIP host is required.
  • Added Bash application/deployment build helpers and bundled archive/hash checks.
  • Existing external-URL installations need a deliberate migration; this packaging change does not automatically migrate them. Full offer staging/certification remains pending.

5 November 2026 — Installation and application refinements

  • Automatic SQL initialization through the app identity on a dedicated SQL server, without a separate customer SQL group or setup service.
  • Six administrator colour themes, draft preview/publication and the visitor light/dark switch.
  • Administrator and member logout return to the public root page and clear only the portal session.
  • Smart365.AI publisher branding and verification of document/AI and Microsoft member workflows with test data.

Updating an installed portal

Publishing a new offer package does not automatically upgrade installed applications. Preserve qualified release archives and customer data backups. Validate schema, identity and behaviour compatibility before an explicit package update.

Package rollback and database/document recovery are separate operations. Full Marketplace acquisition, customer staging, upgrade and recovery qualification must be completed for production releases.