01Who this is for
- Founders who build client facing forms need assurance that custom code cannot expose sensitive data.
- Marketing teams creating survey widgets benefit from automatic blocking of dangerous scripts.
- Web developers customizing quizzes avoid accidental account takeover by receiving instant error feedback.
02HTML editor security validation, explained
When you add an HTML element to a form, survey or quiz, the editor watches the code you type. Any high risk JavaScript, such as direct cookie access, eval, new Function, or string based timers, is detected, a red error appears, and the Save button is disabled. Only safe HTML, standard JavaScript logic, arrow functions, and storage writes are permitted.
The validation runs case insensitively, so variations like EVAL are also caught. If the same issue appears several times, the editor shows one error message. Empty HTML fields and pure HTML without scripts are accepted without restriction.
03How businesses use HTML editor security validation
- Coaching business. A coach adds a custom HTML block to a sign up form to embed a video player. The editor checks the code and blocks any attempt to read document.cookie, ensuring the form remains secure.
- Real estate agency. An agent includes a timer in a property interest survey using setTimeout with a function reference. The editor allows it, but would reject a string based timer, preventing hidden script execution.
- Online education platform. The platform writes user theme preferences to localStorage. Since the editor permits localStorage.setItem, the code saves successfully while any attempt to read authentication tokens is blocked.
04Before you start
- A form, survey, or quiz must be created in the HighLevel builder before editing custom HTML.
05How to set up and use HTML editor security validation in HighLevel
Edit custom HTML with security validation
- Open the form, survey, or quiz builder for the item you want to modify.
- Add an HTML element to the canvas.
- Click the Edit HTML button on the element.
- Enter your custom HTML or JavaScript code.
06Things to know before you rely on it
- The editor blocks high risk JavaScript patterns such as document.cookie, eval, new Function, string based setTimeout/setInterval, and reads from localStorage that expose authentication data.
- Detection ignores letter case, so eval, EVAL, and similar variations are caught.
- Only one error message is shown even if the same problem appears multiple times in the code.
- Pure HTML and safe JavaScript, including arrow functions and storage writes, are allowed.
07If something goes wrong
- Custom code is blocked and the Save button stays disabled.. Remove direct cookie access, avoid eval() or new Function(), replace string based timers with function references, and do not read authentication data from localStorage.
08How it connects to the rest of HighLevel
- HighLevel contact form builder: design, test, and share Contact form builder
- Embedding HighLevel forms on popular website builders Embedding forms
- Configuring email alerts and auto responders in HighLevel forms Email notifications
Michael's take

This feature blocks dangerous scripts before they can damage your account.
Skip it if you never add custom HTML or JavaScript to your forms, surveys, or quizzes.