> For the complete documentation index, see [llms.txt](https://docs.ninjutsugames.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninjutsugames.com/game-creator-2/loot-locker/authentication/white-label.md).
# White Label
## Setup
To enable **White Label** accounts you have to enable it in [**LootLocker's**](https://console.lootlocker.com/settings/platforms/guest) platforms dashboard
Head to the white label login section, enable it and click save.
## Login
To authenticate with this method you can use the **White Label Login and Start Session** instruction.
Here you need to pass in an **email**, **password** and **remember** boolean
## Signup
To signup use the **White Label Signup** instruction.
You need to pass in an **email** or **username** and **password**, if **Verify Email** is on it will if the passed in email is correct.
## Account Recovery
If player forgot the password you can use the **White Label Request Password** instruction.
Only pass the **email** address and this will send an email to user with a link change the password.
## Account Verification
If you account verification enabled players will get an email to verify their account but if for any reason they need to request verification again you can use the **White Label Request Verification** instruction.
---
# 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://docs.ninjutsugames.com/game-creator-2/loot-locker/authentication/white-label.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.