Technical enablement · 03

Feature reference

A catalogue of everything {{product.name}} does. Every entry follows the same structure — what it does, how it works, how it's built and how it's linked — so you can read across the product consistently. Filter by domain or search, and click any entry to expand it.

⚠

Entries below are examples. They illustrate the format for a generic product. Replace them with {{product.name}}'s real features (one entry per user-visible capability), adjust the filter categories to suit, and keep the four-part structure. Remove this callout when done.

Core capabilities

The primary value of {{product.name}}. [Replace: one-sentence framing.]

What it does
[Replace: the user outcome in one or two sentences. Lead with the benefit, then the mechanism.]
How it works
[Replace: the main flow. For example: the user submits input, the service validates it, processes it asynchronously and notifies on completion.]
How it's built
Implemented in the core service; key code under [replace/path/]; configuration keys [REPLACE_KEY].
How it's linked
Depends on [Replace: component]; feeds [Replace: feature]. Switch: features.[replace].
What it does
Brings the customer's existing data into {{product.name}} from files or connected systems, with validation feedback.
How it works
Upload or connect a source, map fields, preview errors, then run. Re-runs are idempotent.
How it's built
Handled by the ingestion pipeline; mapping templates stored per tenant.
How it's linked
Prerequisite for most other features. Source connectors are swappable — see Integrations.

Insight & AI

Analytics and AI-assisted features. [Replace: one-sentence framing, and state any human-review requirements.]

What it does
Answers questions and drafts content grounded in the tenant's own data, with citations.
How it works
A request is enriched with retrieved context, sent to the model provider through the AI service, filtered by guardrails and returned with sources. Users can accept, edit or reject.
How it's built
AI / model gateway; prompt templates versioned in [replace/path].
How it's linked
Uses the search index for retrieval; token usage feeds cost reporting.
What it does
Pre-built and configurable views of key metrics, exportable to common formats.
How it works
Dashboards query curated tables in the analytics store; schedules produce reports on a cadence.
How it's built
Analytics store; chart definitions in [replace/path].
How it's linked
Data freshness depends on the ingestion pipeline. Alerts can be raised from thresholds.
What it does
Suggests next best actions ranked by expected impact.
How it works
Scores candidates using rules and a model, explains the top factors, and records user feedback for tuning.
How it's built
[Replace: service and model], feature flag [REPLACE_FLAG].
How it's linked
Consumes dashboard metrics; actions can start a workflow.

Workflow & collaboration

How teams work together inside the product. [Replace: one-sentence framing.]

What it does
Routes items through configurable review steps before they are published or acted on.
How it works
A workflow definition lists steps and approvers; each decision is recorded with a timestamp and comment.
How it's built
Workflow service; definitions stored per tenant.
How it's linked
Triggers notifications; decisions are written to the audit log.
What it does
Keeps users informed through in-app, email or chat messages, with per-user preferences.
How it works
Events are mapped to templates and delivered through the notification service with throttling.
How it's built
Notification service.
How it's linked
Subscribed to events from most other features.

Platform

Capabilities that apply across the product. [Replace: one-sentence framing.]

What it does
Lets customers sign in with their corporate identity and control what each role can do.
How it works
OIDC login maps identity-provider groups to product roles; sessions are short-lived and refreshed silently.
How it's built
Identity & tenancy; role definitions in [replace/path].
How it's linked
Every other feature checks roles through the shared library.
What it does
Records who did what and when, searchable by administrators and exportable for compliance reviews.
How it works
Services emit audit events; the log is append-only and retained per policy.
How it's built
Shared library emitter; storage [Replace].
How it's linked
Retention rules are agreed with Legal and Compliance, not set by engineering alone.
What it does
Structured logging, tracing and health probes, plus retries and circuit breakers that keep the product stable when dependencies fail.
How it works
Each request carries a correlation id; telemetry flows to the observability stack; breakers open on repeated downstream failure.
How it's built
Observability stack; library helpers in [replace/path].
How it's linked
Basis for the alerts and dashboards in Operations.
ⓘ

For the runtime shape behind these features see the architecture overview; to turn them on in the right order see the implementation flow.