INSPECTOR ARCHITECTURE · CURRENT STATE AND BOUNDARIES

A lightweight Dynamics tool first. A saved workspace only when you need one.

Inspector starts inside the Dynamics browser session an operator already uses. The scan is read-only, on demand, and locally reviewable without an Anselith account. Saving a minimized result is optional. The broader Atlas architecture supports that save path and a separate CPQ beta; it is not a claim that a connected product suite is available today.

01

One public product, with Labs kept separate

Current state, not portfolio theater

Anselith Inspector

Free public beta

The public beta supports on-demand Dynamics 365 scans. Local results need no Anselith account; saving the minimized projection is optional. Scheduled monitoring and additional sources are not available.

Review current tools →

CPQ

Separate private beta

Invited Labs users can configure deterministic quotes and use the current discount approval. CPQ is not included in the Inspector public beta.

Review Labs boundary →

Relationship, contract, revenue, and platform intelligence

Planned concepts

These are roadmap families. Any interactive views use synthetic data and are not connected customer products.

Review Labs boundary →

Assistant and Executive Command

Synthetic previews

These experience studies illustrate a possible future composition model. They are not production assistants, monitoring, or executive reporting.

Review Labs boundary →
02

One current path, four responsibilities

  1. 01

    Dynamics 365 in the browser

    Inspector sends GET requests through the signed-in operator's current session. The public beta does not require an app registration or a server-side Dynamics connector; restricted-role acceptance is still open.

  2. 02

    Local operator result

    Current tool modules run on demand and show findings locally. No Anselith account is required to see that result, and Inspector does not remediate CRM records automatically.

  3. 03

    Optional workspace save

    A signed-in operator can choose to send a minimized projection to the tenant-scoped Inspector workspace built on Atlas. Saving is separate from scanning and is not continuous monitoring or a shared team queue.

  4. 04

    Labs, separately

    CPQ has its own private-beta workflow. Product-family and experience previews are synthetic roadmap studies; they do not inherit Inspector's public-beta status.

03

Capability truth table

Session-bound browser scanFree public beta
Read-only Dynamics requests through the operator's existing browser session, with local results before account creation.
Optional Atlas workspaceBeta
Authenticated storage for the minimized result projection. Tenant-scoped records and audited action infrastructure are live; saved Inspector history remains a beta surface.
Governed product actionsCPQ private beta
Product-specific Atlas actions support the separate CPQ beta. Inspector itself does not write to Dynamics.
Additional sources and compositionPlanned
Server-side connectors, cross-system identity resolution, shared team workflow, Assistant, and Executive Command are not shipped.

CONNECTION TRUTH

Dynamics 365 today. No implied connector catalog.

Inspector uses the signed-in user's Dynamics browser session and issues read requests. It does not currently connect to Salesforce, an ERP, a contract repository, or infrastructure telemetry. Those sources remain possible Labs requirements, not shipped integrations.

Review the browser and data boundary

Start with the useful part

Run the local scan. Decide about a workspace later.

The free public beta needs no account for local results and no card.