> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/agency-white-label/customers/access-customer-information.md). # Access customer' information ### How to access or log in to a customer’s account? The Agency dashboard allows you to log in to a customer's account to view or troubleshoot their app setup. This is useful for providing assistance or reviewing their configuration directly. {% embed url="" %} #### Step 1: Go to the “Customers” * Navigate to the Customers tab from the side menu * This section lists all customers along with their activity and account details #### Step 2: Search for the customer * Use the search bar to find the customer by name or email * You can also apply filters to narrow down the list #### Step 3: Open the login option * Locate the customer you want to assist from the list * Click the Login as customer button next to their entry {% hint style="success" %} This feature allows you to access the customer’s view without needing their login credentials. {% endhint %} #### Step 4: Access the customer dashboard * You will be redirected to the customer's dashboard in a new tab or session * You can now view their app, settings, and perform actions on their behalf --- # 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.appmysite.com/agency-white-label/customers/access-customer-information.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.