Platform Release Notes: Knowledge Center & Developer Portal Launch

This release adds a connected documentation and discovery layer across SAVHN: the Knowledge Center, this Documentation Portal, the Developer Portal, standalone module pages, and cross-linking between Industry Clouds and the modules that power them.

What's new

Knowledge Center

A searchable library of how-to content, now accessible from Documents → Knowledge Center as well as from a public-facing entry point for prospective customers. The Knowledge Center is aimed at task-level "how do I..." content — shorter and more example-driven than the Documentation Portal's reference-style pages.

Organized by module, with cross-links into the Documentation Portal for deeper reference material.
Searchable from global search alongside your organization's own records.
Content here is platform-maintained; organization-specific internal guides remain a separate concern for admins to manage through Documents.

Documentation Portal (this section)

A structured reference covering administration, end-user workflows, developer integration, architecture, deployment, security, and troubleshooting — organized into the sections you're reading now (Admin Guide, User Guide, Developer Guide, API Reference, Architecture, Deployment, Security, Troubleshooting, Release Notes).

Every page is cross-linked to the specific modules and, where relevant, Industry Clouds it applies to.
Content is versioned independently of the product release cycle, so documentation can be corrected or expanded without waiting for the next platform release.

Developer Portal

A dedicated surface for anyone building against SAVHN's API, covering:

API credential generation and revocation, scoped per integration.
Webhook endpoint registration and a delivery log for debugging failed deliveries.
A live schema explorer alongside the static API Reference documentation page.

The public /developers page now links directly into this Documentation Portal's API Reference (/docs/api-reference) as the canonical starting point for new integrators, alongside the Developer Portal's credential management tools for existing customers.

Standalone module pages

Each of the platform's modules (CRM, HRMS, Payroll, Finance, Projects, Tickets, Timeline, Meetings, Chat, Documents, Client Portal, Reports, Learning, Skills, Automations, Marketplace, and the AI & Intelligence modules) now has a dedicated marketing/reference page describing its capabilities, independent of the Module Marketplace's operational enable/configure flow. These pages are the natural landing point for prospective customers evaluating a specific module, and they cross-link into the relevant Documentation Portal pages for operational detail.

Industry Cloud cross-linking

The 22 built Industry Clouds now cross-link bidirectionally with:

The specific core modules each Industry Cloud bundles and configures (so a visitor reading about the Construction Industry Cloud can jump straight to the Projects or Finance module page to understand the underlying capability).
Relevant Documentation Portal pages, where an Industry Cloud's setup depends on concepts covered generically elsewhere (e.g. module dependencies, role configuration).

This closes a navigation gap where previously a visitor evaluating an Industry Cloud had no direct path into the generic module or documentation content explaining how the underlying capability actually works.

Why this release matters

Prior to this release, documentation existed but wasn't discoverable as a connected system — module pages, industry pages, and reference documentation were effectively separate islands. This release ties them together so that:

A prospective customer can move from an Industry Cloud page → the modules it bundles → the Documentation Portal pages explaining setup, in a continuous path.
A developer evaluating the platform can move from the public Developer page directly into the full API Reference without a support handoff.
An existing customer's admin can find operational guidance (role management, module dependencies, troubleshooting) without leaving the product's own navigation.

How the pieces relate to each other

It's worth being clear about how these four surfaces differ, since they can look similar at a glance:

Surface	Audience	Content style
Knowledge Center	Existing users, in-product	Short, task-focused "how do I..." articles
Documentation Portal (this section)	Admins, developers, evaluators	Structured reference content, organized by section
Developer Portal	Developers and integration partners	Operational tools (credentials, webhooks) plus a live schema explorer
Module pages	Prospective customers, evaluators	Capability-focused, marketing-adjacent overviews per module

A useful way to think about the relationship: the Knowledge Center answers "how do I do this specific thing," the Documentation Portal answers "how does this system work and what are the rules," the Developer Portal is where you actually operate API access, and module/industry pages are where you first learn what's possible before either reference surface becomes relevant.

Migration notes for existing content

If your organization had previously bookmarked or linked directly to older documentation locations, note that:

The Developer Portal's API credential and webhook management tools remain in the same location as before this release — only the reference documentation and public-facing entry points changed.
Any internal documentation your organization maintains that referenced generic platform behavior (authentication flow, RBAC mechanics, module dependency rules) can now safely link to the relevant Documentation Portal page instead of re-explaining it, reducing the maintenance burden of keeping internal docs in sync with platform behavior.

A note on how documentation is maintained going forward

With this release, the Documentation Portal becomes the source of truth for platform-wide operational behavior (authentication, RBAC mechanics, module dependencies, and so on), separate from and versioned independently of the underlying product release cycle:

Corrections and clarifications to documentation content can ship without waiting for the next product release, since this content is not compiled into the application build.
Each page in this portal is independently addressable (linkable by its slug, e.g. /docs/api-reference) and independently maintained, which is what allows external surfaces like the public Developer page to link directly and reliably to a specific page rather than a general documentation area that might reorganize underneath it.
Because pages are cross-linked to specific modules and, where relevant, Industry Clouds, keeping those relationships accurate as new modules and Industry Clouds ship is treated as part of this documentation's own maintenance — a newly added module should also show up as a cross-link on the documentation pages that reference it.

What to check after this release

If you're an Org Admin:

Review the Getting Started for End Users and Organization Setup & Onboarding pages against your own onboarding process — these are now the canonical reference your new hires and admins will find if they search for help.
If your organization has custom internal documentation, consider cross-linking to the relevant Documentation Portal pages rather than duplicating platform-wide content (like API conventions or RBAC mechanics) internally, since platform-wide content here is maintained centrally.

If you're a developer or integration partner:

Bookmark /docs/api-reference — it is now the stable, linked destination from the public Developer page.
Review Developer Portal Overview and Building Integrations with SAVHN for the current authentication and webhook patterns before building or updating an integration.

Developer Portal Overview
API Reference
Building Integrations with SAVHN