The Check button and send guard

On a site you use every day, you can put a small Check with Prismlet button on the page itself. The same setting turns on the send guard: when you press Send, Prismlet checks your text first and holds the send, or asks you to confirm, when your team's rules say so. You turn both on per site, from the side panel. Your admin decides which answers hold the send; Send guard covers their side.

Turn it on for a site

1. Open a page of the site and open the side panel by clicking the Prismlet icon.
2. Open the panel menu (...) and tick Show the Check button on this site.
3. Chrome asks once whether Prismlet may read and change that site. Allow it.

The panel then says The Check button shows beside composers on this site, and Send waits for your reviews. The button appears in the current tab at once. Other tabs of the site that were already open get it when you reload them.

The setting appears only on a page one of your reviews covers. When a review there can hold or warn and the button is still off, the menu adds Turn it on so Send waits for the reviews that can hold or warn.

Prismlet asks for access to that one site, not to every site. If you decline Chrome's prompt, the panel says Prismlet was not allowed on this site. and the setting stays off. The button works only on sites served over https.

The setting stays on after you restart Chrome, until you turn it off or sign out.

The Check button

A Check with Prismlet button sits at the bottom-right corner of each composer Prismlet finds on the screen. Clicking it opens the side panel, reads that composer and runs every check for the screen, the same as Check in the panel. The answers show only in the panel, never on the page.

The button shows a short state for its own composer:

Button says	Meaning
Opening Prismlet...	The panel is opening.
Open Prismlet to see results	Chrome did not open the panel. Click the Prismlet icon in the toolbar, and the check starts when the panel opens.
Checking...	The checks are running.
Done - see panel	Every check finished. Read the answers in the panel.
Check failed - see panel	At least one check could not run, or an input was missing. When an input is missing, nothing is sent. The panel says why.
Prismlet is busy - try again	Another check was running. Click again when it ends.
Changed since last check	You edited the text after the check. Click to check again.
Prismlet unavailable	The check could not start, for example because you are signed out. Open the panel, sign in if needed, and reload the page.

A check started from the panel updates the button of the composer it read, too.

The send guard

The send guard works on screens whose reviews can hold the send or ask for a confirm, once the Check button is on for the site. When you press the screen's Send button, or a send shortcut such as Ctrl+Enter in the composer, Prismlet stops the send, reads that composer and runs its checks. The button says Checking before send... while they run. Then:

• If nothing needs your attention, the send goes through on its own.
• If an answer holds the send, the send stays held.
• If an answer asks for a confirm, Prismlet asks you before sending.

The answers of a guarded send also show in the panel.

Send held

The composer's button turns red and says Send held - see Prismlet. Hover it to see the reason, such as the prism, the question and its answer. Click it to open the panel on the answers.

Fix the text and press Send again. Prismlet checks the new text before it lets the send go.

Confirm before sending

A box beside the composer gives the reason and two choices:

• Go back keeps the send held, so you can change the text.
• Send anyway sends the text as it is.

Prismlet asks for a confirm when:

• an answer is under Confirm before sending
• an answer is Unsure on a question that can hold or warn
• a check could not run
• the checks did not finish within 20 seconds, with The checks did not finish in 20 seconds.
• another check was still running, with Prismlet is still checking this page.
• you are signed out, with Prismlet is signed out, so this text was not checked.

What Send anyway records

Send anyway records the time on each result of that check, and the Prismlet app shows it on each result. Your team can see that you sent the text after Prismlet asked you to confirm. When no check finished, as after the 20 seconds, there is no result to record it on.

What the guard cannot catch

The guard catches a press of Send on a page where it runs. It does its best, and some sends get past it:

• a scheduled send, and a send that goes out later after an undo-send delay
• a send from another device, or from a Chrome where you are not signed in to Prismlet or the button is off
• a tab of the site that was open before you turned the button on, until you reload it
• a send through any other route the site offers, such as a menu item or a different button

The guard helps you catch mistakes. It does not replace reading your text.

On some sites the text does not send after Prismlet lets it through or you choose Send anyway. Turn the Check button off for that site to send, and tell your admin, because the site needs a different setup.

Turn it off

Open the panel menu (...) on a page of the site and clear Show the Check button on this site. The panel says The Check button is off for this site. Prismlet removes the button and the send guard, and gives the site access back to Chrome. Other open tabs of the site lose the button when you reload them.

Signing out with Disconnect this browser, or a sign-in that ends, turns the Check button off on every site at once.