Skip to main content

Roadmap

Where Kybera Impact is heading next, and what's just landed. The dates below signal direction, not commitment — for timing on a specific capability, work with your Kybera Impact provider.

Recent updates​

The platform has shipped a steady stream of capability over the last several weeks. The shifts that matter most to your organization:

Governance health, redesigned​

The audit engine now produces a single Governance Score from 0 to 100 for every Kybera Impact-managed workspace, rolled up from five continuous KPIs. Every workspace gets a clear status — Strong, Moderate, Gaps, or High Risk — plus plain-language findings tagged Critical, Warning, or Info that explain exactly why the workspace scored where it did. A dedicated Audit Issues list captures library-level problems across the tenant, so cross-tenant slices ("every stale library in Operations", "every schema-drift library this month") stay fast at scale.

Tenant reconciliation​

Kybera Impact now keeps the workspace registry in lockstep with what's actually in your SharePoint tenant — in both directions:

  • Forward drift (registry says alive, the site is gone) is caught by the audit and reconciled automatically.
  • Backward drift (the site is alive, but the registry doesn't have a row for it) is caught by a monthly tenant-reconciliation pass that rebuilds missing rows from the live site.

Whatever a tenant admin does outside the normal flow — restoring sites from the recycle bin, deleting registry rows manually, importing legacy sites — the platform reconciles it.

Disposed-workspace cleanup​

A scheduled cleanup pass keeps the registry tidy after disposal. Disposed workspaces stay visible for a configurable retention window (90 days by default) as an audit trail, then are removed via SharePoint's list recycle bin — recoverable if needed.

Workspace lifecycle, end-to-end​

The full lifecycle — Archive, Unarchive, Dispose — now ships for both Teams-connected workspaces and SharePoint-only workspaces. Six coordinated operations across Microsoft Teams and SharePoint, with the platform handling the coordination so your team doesn't have to.

Business Authority change​

A workspace's business owner can be updated through a governed flow. Changes flow through the compliance pipeline and apply point-forward to the workspace's property bags and registry row — so brokers, audit, and Insights reflect the new ownership automatically.

Workspace title sync​

If a workspace's SharePoint site title is changed, compliance now keeps the registry row's title in sync automatically. The registry stays accurate without manual reconciliation.

IM Portal: enterprise content types and site columns​

The IM Portal now manages the full enterprise content-type model. Your IM team can export, edit, import, and publish enterprise site columns and content types directly from the app — no tenant-level SharePoint admin escalation required. Bilingual taxonomy management is unchanged; site columns and content types simply extend the IM Portal's reach.

Bilingual emails end-to-end​

Every email notification the platform sends — request submitted, broker review, provisioning complete, lifecycle action complete — is now bilingual, per recipient, based on the recipient's Microsoft 365 profile language. No English fallback for French recipients; no separate template paths to maintain.

Near-term plans​

Records management module​

The next major addition to Kybera Impact. The records-management module will bring structured retention schedules, records declaration workflows, records-centre integration, and end-of-retention disposition into the same platform that already handles workspaces, libraries, and Business Authority.

The foundations are in place today: Business Authority metadata flows through provisioning and compliance, retention labels can be applied through templates and Purview, and workspace lifecycle supports archive and dispose states. The records module will add the records-specific orchestration on top.

Ongoing evolution​

Beyond discrete new modules, the platform continues to refine its existing capabilities:

  • Insights depth. Additional KPI breakdowns and cross-tenant comparisons as the audit model matures.
  • Template refinements. New template capabilities as Microsoft 365 introduces new SharePoint and Teams features.
  • Bulk provisioning enhancements. Expanded scenarios for organization-wide rollout and reorganization events.
  • Multilingual coverage. Additional languages beyond English and French as client demand drives them. The architecture supports extension; specific languages follow real requests.
  • Integration breadth. Deeper integration with Microsoft Purview, Microsoft Copilot, and other emerging parts of the Microsoft 365 stack.

What's not on the roadmap​

A few clarifications on the boundaries:

  • Replacing Microsoft Purview. Kybera Impact extends Purview for operational scale; it doesn't replace Purview's labels, policies, or compliance scanning.
  • Content-inspection. Document-level inspection — DLP, sensitive-data detection, insider risk — stays with Purview and Microsoft Defender.
  • Platforms other than Microsoft 365. Kybera Impact is built specifically for Microsoft 365. Other collaboration platforms are out of scope.

Where to go next​