> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/publish/site-audience/authenticated-access/enabling-authenticated-access.md). # Enabling authenticated access To protect your docs behind a sign-in screen, you’ll need to first enable authenticated access for your site. ### Enable authenticated access Head to your [site’s settings](/docs/manage-your-site/site-settings.md), and choose **Authenticated access** from your site’s audience settings. Once selected, you’ll see a few options you’ll need to continue configuring your site. You’ll also see a generated "**Private key**", which you’ll need at a later point in the authenticated access setup. ### Choose an authentication method Depending on your setup, we have integrations and guides on setting up authenticated access for different tools. Head to the relevant guide to continue setting up authenticated access for your site.

	Cover image		Cover image (dark)
Setting up Auth0	25_12_10_auth0_1.png	Setting up Auth0	25_12_10_auth0.png
Setting up Azure AD	25_12_10_azure_1.png	Setting up Azure AD	25_12_10_azure.png
Setting up Okta	25_12_10_okta_1.png	Setting up Okta	25_12_10_okta.png
Setting up AWS Cognito	25_12_10_aws_cognito_1.png	Setting up AWS Cognito	25_12_10_aws_cognito.png
Setting up OIDC	25_12_10_oidc_1.png	Setting up OIDC	25_12_10_oidc.png
Setting up a custom backend	25_12_10_custom_1.png	Setting up a custom backend	25_12_10_custom.png

--- # 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://gitbook.com/docs/publish/site-audience/authenticated-access/enabling-authenticated-access.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.