Inspector sends GET requests through the Dynamics session the operator already has. A local scan needs no Anselith account. Saving is optional, requires Anselith authentication, and sends a minimized projection to tenant-scoped storage. The controls below describe the public beta as it exists today, including the browser-token tradeoff.
Inspector can show a scan locally without an Anselith account. If an operator chooses to save, Supabase Auth establishes the session and tenant-scoped rows carry account_id behind row-level security. Interface filtering is not the storage boundary.
The public-beta extension issues read requests to Dynamics. Saving sends a minimized projection to Anselith; it does not edit source records. The separate CPQ private beta uses governed Atlas actions for quote and approval writes.
Inspector uses the operator's existing Dynamics browser session, not an Anselith-held Dynamics password, client secret, or app registration. Optional saving uses the operator's Anselith access token. No general server-side Dynamics connector is being claimed.
Atlas stores action invocations and audit events. Current Atlas record tables also capture temporal versions so an authorized reader can inspect prior state and as-of views. This is operational history, not a claim of certified or immutable archival storage.
Where currently instrumented, Sentry receives application errors, PostHog receives defined product events, and Cloudflare provides runtime logs. Coverage differs by surface. Inspector disables session recording and broad click autocapture; this is not a claim that every field can never reach a log.
Inspector is the sole public-beta product. CPQ is a separate private beta. Other product families and shared experiences are planned or synthetic, so their proposed controls are not presented as shipped safeguards.
Inspector is a browser-based operator tool. It reads through the signed-in user's Dynamics session and displays the scan locally. An Anselith account is needed only for the optional save step. It is not a general server-side connector and does not describe how possible future CRM, ERP, contract, or telemetry connections would work.
Inspector introduces no app registration or service identity, and it does not write remediation back to Dynamics. Restricted-role response behavior remains an explicit public-beta acceptance test rather than an independently verified claim for every role.
Inspector's Dynamics source scan is read-only. CPQ is a separate, invite-only Labs beta where configuring a quote and recording an approval are the work. Those CPQ operations use the governed Atlas action path; they are not Inspector capabilities.
A signed-in, entitled CPQ private-beta user initiates the operation.
The SDK sends the user's bearer token to the product or platform API.
The action executes in tenant context and row-level security limits the records it can reach.
Validation, authority rules, idempotency, and audit are handled inside the transaction.
Direct record-table writes from an authenticated client fail closed outside the action gate.
Marketing, portal, and first-party web applications.
Platform and product HTTP services, with service bindings used only for internal Worker-to-Worker calls.
Current project region: us-east-1. Tenant isolation is enforced with Postgres row-level security.
Errors, product events, and runtime diagnostics are handled separately.
First-party TypeScript applications use this platform plane. A future federated or polyglot product may run elsewhere and must meet the same identity, tenancy, entitlement, and observability contract. Anselith does not currently claim SOC 2 certification or customer-selectable data residency.
Start with Inspector's browser and data boundary above. If you are evaluating the separate CPQ private beta or a planned Labs concept, request the security scope for that specific surface; this page does not extend Inspector's claims to those products.