One home for your form’s intelligence.

Start with the right workspace.

Sign in to the FormLint app using the magic link sent to your email. First-time access depends on the installation’s registration settings: you may need an invitation. Create or choose a workspace to get started.

A workspace contains your projects, team, keys and usage. Use the workspace menu at the top of the sidebar to switch between workspaces you belong to. Check the selected workspace before changing a project.

Open your account menu at the bottom of the sidebar to update your name and avatar in Profile, or to log out. Profile details describe you across your workspaces.

Each form gets a project.

Open Projects and select New project. Give it a recognizable name, such as “Packaging quote.” Owners and admins can create projects and save their configuration.

In Configuration, expand Form setup to edit the form name, allowed field names, allowed origins, default language and suggestion timing. Add a starter pack or create a rule, then save. Draft edits and message previews do not change your connected website until you save.

Use one project for a form configuration. A project can allow several website origins, for example staging and production. Use separate projects when forms need different fields or rules. Learn how to configure the intelligence.

Try the rules you have saved.

1. Save a valid configuration and create an active public key.Both are needed for the project playground.
2. Allow the app’s origin.The playground runs on the dashboard host. Include its exact origin in the project while testing, alongside your website origin.
3. Open Playground and check the connection.Live evaluation must be enabled on the evaluation service. If it is not connected, use Reconnect after the service is available.
4. Type a non-sensitive example.Wait for the configured typing pause, read the feedback, then add the missing details. Test incomplete, complete and ambiguous answers.
5. Check the language.Use Widget language to try English, Italian or Auto. Missing translations fall back to the project default.

The playground evaluates answers through the live service when connected, so evaluations can use workspace quota. Its Submit demo button only confirms a local preview submission; it does not send a submission to your website’s destination. Evaluation before submission is a separate operation.

Save rule changes before returning to Playground. The editor’s message preview only shows the wording; it does not evaluate an answer. For fixture-based examples that do not call a live provider, visit the public simulated forms.

Find the right connection.

For code you maintain, start with the React, Vue or JavaScript guide. All three use the same SDK.

The app’s Integrations area contains official downloads and guides for Elementor, Gravity Forms, Tally and Framer. Elementor and Gravity Forms share a WordPress plugin. Tally uses custom-domain code injection, and Framer currently uses a developer plugin installation. Check the platform’s requirements in its guide.

Every connection needs a public project key, the evaluation endpoint, the allowed origin and a mapping between your form’s inputs and the saved project fields. Webflow and other WordPress forms can use the JavaScript connection.

Give people the access they need.

Owners and admins manage the workspace in Settings. Rename it under General. Open Users to invite someone by email as a member or admin, review members and pending invitations, or manage eligible roles and access.

Owner membership is protected. The member list does not let you remove yourself or change your own role. Invitations must be accepted by their intended recipient; email delivery requires the installation’s email service to be configured.

Use the right kind of key.

Public project keys belong in website integrations. Create them in the project’s Installation & keys tab. They identify the project and work with its saved origin allowlist.

To rotate a public key, create a replacement, update the connected form and verify it, then revoke the old key. Revocation stops suggestions for installations still using that key; their original form submission remains available.

Private workspace keys are managed in Settings → API keys. They are backend credentials, shown once when created. Give each a useful description and keep it in your server’s secret storage. They do not belong in the browser SDK, builder settings or injected snippets.

Understand what is being counted.

Usage shows evaluation reservations across the selected workspace, its quota and recorded outcomes. A reservation consumes an evaluation allowance when processing is authorized. A later unavailable result can still have a reservation; retrying the same request ID does not reserve another credit.

These are processing records, not a count of submitted forms, leads or conversions. FormLint does not provide an archive of raw visitor answers. In self-hosted mode, the usage period is the current UTC calendar month and limits are set by the server operator.

Settings → Billing reflects the installation’s mode. Self-hosting does not require a Cloud subscription. Paid controls are available only when billing is configured, and only to owners and admins.