More control over how people explore a knowledge base

Premium adds a Profiles hub from which administrators can create and manage several knowledge profiles. Each profile has its own configuration, connection test and status.

Access can be public, limited to signed-in visitors, restricted by role or granted to named users. An unavailable or unknown profile should fail closed rather than fall back silently to another knowledge source.

Not every useful interaction should begin with an empty question box.

Premium lets an owner create authored questions with stable keys, organise them into ordered collections, place a full panel, a single question or a collection through WordPress, and share links that arrive with a question already prepared.

This makes the question interface a publishing surface as well as a search box. The owner decides which routes through the knowledge are worth making visible.

Premium can add owner-approved evidence links beneath answers, and chronology records containing dates the owner has verified. These are governed additions, not provider citations inferred automatically.

A profile can also send a bounded number of earlier turns as context, so follow-up questions can stay coherent. The setting is explicit and per profile rather than an assumption built into every conversation.

Some questions are asked repeatedly and do not need a fresh provider call every time. Premium can store owner-approved question-and-answer pairs and serve them directly while the relevant identity still matches.

The important part is the approval and invalidation boundary. A cached answer should not stay authoritative after the configuration that gave it meaning has changed.

Premium extends conversation administration with per-profile recording and retention controls, export to CSV and Markdown, typed-confirmation erasure and an audit record of relevant governance actions.

These controls are for an administrator who needs to understand not only what visitors asked but how those records are retained, exported or removed.

Although Premium is a separate plugin, its capabilities are hosted through Core’s administration patterns. Profiles, governance, settings and response colour controls appear as one working environment rather than a second dashboard with a competing design language.

That reflects the architecture: separate responsibility in code where the boundary is useful, one ordinary product experience where it is not.

NCI Premium is not publicly available. Pricing, licence terms, purchase and delivery have not been decided, and nothing on this page should be read as an offer. The capabilities above were exercised with a live OpenAI connection on a WordPress test installation on 17 October 2026; that is local acceptance, not release.

Read about the free Core plugin, or the case study that explains how the two came to be separate.