Assay Lens + Assist · Chrome extension

The findings, on the card, while you build.

Lens badges the cards with a problem in the Okta Workflows designer. Assist shows the fix, reviews your change and helps design the next flow.

Get a free Lens key Lens + Assist plans

Checking never writes to Okta Checks run on your Assay server A key per browser

Assay Lens in the Okta Workflows designer: findings badged on the cards of a leaver flow, the Read User card's findings open with a better way to build each, and the side panel with the flow's grade D, 9 High, 9 Medium and 1 Low across it and the two helper flows it calls — Lens in the real Okta Workflows designer, on a demo leaver flow built to show the checks (never switched on). Badge and panel are unedited Lens output; only the signed-in account is hidden.

How Lens works

Open a flow. The problems are already marked.

Lens reads it, with the helper flows it calls. Click a badge for the finding and the fix; save, and it checks again. Same engine as the full assessment.

Failure paths Calls that can fail uncaught, and access changes left half-made when a later step fails.

Unchecked results A search result used without checking it found anything; If/Else paths that do nothing.

Hard-coded values Okta ids, endpoints and addresses in cards, which stop a clean move to production.

Your naming standard Flow and card names checked against the standard your workspace sets.

Assist

From “what is wrong” to “how to build it right”.

In the Lens side panel and your Assay workspace. It runs on your Assay server; the extension only shows the answer.

Fix guide Every problem in the flow and its helpers, with the cards to add and how to set them. Each fix links to real uses in Okta’s published templates.

Change review and sign-off Cards changed, findings added or fixed, grade before and after. A risky change goes to someone else to approve.

Design help Describe the process; get the trigger, the flows, each card in order, the tables, and what happens when a step fails.

No AI model to connect Runs on Assay’s own engine and pattern library. It reads card names, never field values or credentials.

When Assay can make the fix itself, Assay Studio makes it on your export and hands the file back, assessed again first.

Assist fix guide: where the flow is worst to fail and the steps to make it safe — Fix guide: where the flow is worst to fail, what that leaves half-done, and the cards that make it safe.

Lens Free · read-only, unless you push

Get a key.

We confirm your email, approve the request by hand (usually within one working day), then send a link that shows your key once, with the download.

Findings on the card, for one builder, up to 150 flow checks a day Read-only: it never changes anything in Okta. The open flow is assessed in memory on your Assay workspace and not kept. Your key is shown once. We keep only a hash of it. Push, for Enterprise: Studio-built flows into the open folder. New flows only; it never switches one on.

Already a customer? Ask at your own workspace address instead: your-company.app.theassayco.com/lens/request. More on what Lens reads: FAQ.

Build it right the first time.

Start with Lens Free. Add Assist with the Build plan, or the full assessment with a Workspace.

Get a free Lens key See pricing