# Login 🔑 * [ ] Logo Either your complete logo or a symbol mark * [ ] Title Tell the user this is where they login * [ ] Account identification A unique identifier for the user ⭐️ Consider multiple identifiers to login with e.g. username, or email address, or phone number * [ ] Password A secure, private code that allows access to their account ⭐️ Create the ability to make the password visible * [ ] Link to reset password A user may forget their unique code - let them change it! ⭐️ Position this link close to your password input field * [ ] Login via third party Turn text fields into one click by allowing users to connect via a third party e.g. Google, Apple, Facebook, Twitter * [ ] Testimonial Reinforcing the brand and product never goes out of style * [ ] Blog post An opportunity to show off content relevant to the user * [ ] New feature The perfect way to build excitement for something new right before a user is about to log in and see it --- # Agent Instructions: 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: ``` GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/pages/login.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.