While building a form you can mark the form as authenticated, so that only the original responder can fill in the form and edit their response.

Make the form authenticated

How to access responder’s dashboard

Access to previous responses

Using authentication for HTML Forms

Authorized forms in Webflow

Loading element

Show specific page elements when the user is logged in / not logged in

Now when a responder will open the authenticated form, they will be redirected to the sign up page. They should create the responder’s account or use the existing one. After sign in / sign up, the user will be redirected back to the original form and can create the response.

The users can sign in directly by using the link: https://app.formli.com/responders/sign_in

After signing in, the user can view their dashboard at https://app.formli.com/responders. Here, they can change their password and sign out of the application.

After signing in, users can fill out the form as many times as needed. It will be available until the user signs out. Responders can also access their previous responses via the Response URL link (see the help article here). Users will have access only to their responses; all edits to the form will require permission.

The creator can open the form without an additional responder account.

You can make HTML forms authorized (detailed guide on how to use HTML forms - link). If you choose to copy and use the generated code, the authorization tags will already be added. Each form should contain the data-os-authenticated="true" tag.

The authorized form should also have an element which will be shown when the user isn't authorized: data-os-element="unauthenticated" with class="os-hidden".

If you are connecting Formli and Webflow elements manually (see here), you should change the link for data-os-element="unauthenticated" .

The final link should follow the template:

https://app.formli.com/responders/sign_up?return _url=https://irynas-tests.webflow.io/auth-forms where https://irynas-tests.webflow.io/auth-forms is address of the page where the form is added.

For using authorized HTML forms you should add you domain as authorized origin in the Domain settings of your workspace (guide).

To prevent the responder from seeing the actual fields until they sign in, you can add loading element data-os-element="loading" that will be shown while the page is loading. You can assign it to a specific form on the page by using data-os-for tag. If you don’t specify data-os-for it will take the first loading element on the page.

If you need to display an HTML element only when a user is logged in, you can add the tag data-os-element="authenticated" to any element. For elements that should be shown to users who are not logged in, use data-os-element="unauthenticated". This way, you can show and hide multiple elements on the page based on the user's login status.