> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/require-login-to-forms.md). # Require Login to Forms Enable login for dashboard users to authenticated forms for your organization ## Overview By adding authentication to a form, you can restrict form access so only specific users with access to your Feathery account can view and submit it. This is separate from logging into the Feathery dashboard as it controls who can access your published forms, not your account. Users can authenticate via email-based login or single sign-on (if it's enabled for your account). They must first be added to your Feathery account. Form authentication also unlocks secure form features and enables you to have greater control over who sees and submits your form. ## Authentication Types Feathery supports two primary methods of authentication: * Email Login * SSO To enable form authentication, navigate to "User Tracking" tab within the form settings. There, you'll find the "Require Authentication" dropdown where you can choose the method of authentication you want the form to support.

## Provisioning User Access To give users access to your authenticated form, you need to [add them to your team](/platform/account-settings/managing-your-team.md#adding-users). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.feathery.io/platform/build-forms/require-login-to-forms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.