By default SilentShield finds your forms itself. If you want to decide which forms are protected, you write rules. This post shows where they live and how to add one. The film below shows it on the real dashboard with sample data, silent and with short captions. The text under it says the same in words, so you can follow along without playing the film.
The film in short
The film opens “Edit API key”, switches “Form Detection” from “Automatic (Beta)” to “Manual”, adds a rule in the “Form Editor” with the pattern “form#checkout”, shows the same rule in the “JSON Editor” and ends on “Save changes”. It does not run the rule against a live page. It has no sound and does not start by itself.
Step 1: open the key and switch to Manual
Open your key and choose “Edit API key”. Under “Form Detection” you will find “Automatic (Beta)” and “Manual”. Rules only appear once you pick “Manual”: then a section “Form Rules” opens with the text “Define which forms should be protected.”
Step 2: add a rule in the Form Editor
The “Form Editor” tab has three fields and a button. “Matches on” says how the rule finds a form (“CSS Selector” is preselected), “Pattern” is what it looks for, for example “form#checkout” or “form[name=contact]”, and “Protection” says what happens (“Protect”). Press “Add Rule”. The rule now appears in a list with its pattern and the “Protect” badge, and you can edit or remove it.
Step 3: look at the JSON Editor
The “JSON Editor” tab shows the same rule as text, with the fields the editor fills in for you, such as a name, the mode, what to do on failure and the thresholds. This is handy if you want to copy rules to another key or edit several at once.
Step 4: save
Press “Save changes”. The dashboard confirms with “Saved — The API key was updated successfully.” Until you save, nothing is applied.
Test a rule before relying on it
Open a rule and use “Test Rule (Dry-Run)”: you enter the URL of a page of your site, and the test tells you whether the rule finds a form on it. The dialog notes that the page must be publicly accessible from our server, because our server fetches it, and the page has to belong to the domain of the key. The documentation page for form rules lists all matching options.
What the film does not show
The film does not run the test against a live page and makes no statement about how many forms a rule will find on your site. How you check that the protection reaches your server is shown in add the server-side check.