> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/settings/login-screen.md). # Login Screen The first thing your app's users will see when they load your Noloco app will be the login screen, until they log in. Therefore, a crucial step in sharing your app is customizing the login screen. You can do this from the **Login Screen** settings page or by clicking this link: On this page, you can * Change the login page title (Business only) * Change the login page description (Business only) * Change the login page logo
### Customizing the login screen title & description {% hint style="info" %} Customizing the login screen title and description is only available on the **Business** plan {% endhint %} On the **Business** plan, customizing the login screen's title and description can allow you to provide specific instructions to your app's users, and build better trust with them that the page they're on is the correct page. ### Customizing the login screen logo As you saw in [Customizing App Logos](/~/revisions/4ycMT0EcUe4aYSGLpT5Z/settings/general-settings/custom-logos.md) you can customize the logo that appears on your app's login screen. The login & email logo is used when you're on the Login page, the Registration page, the accept invitation page and the forgotten password flow. These pages have a light background so you should use a logo which is darker. In the example below the logo used is darker than the one above. It is also the logo used when sending emails from Workflows, account invitations, or for comment notifications.\ \ We recommend using a logo that is 128px tall and less than 192px wide. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.noloco.io/~/revisions/4ycMT0EcUe4aYSGLpT5Z/settings/login-screen.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.