> For the complete documentation index, see [llms.txt](https://docs.alphageo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphageo.ai/client-onboarding-guide.md).

# Client Onboarding Guide

Welcome to AlphaGeo.

Use this guide to complete your initial setup and start using the platform with confidence.

### 1. Login credentials

Login credentials are sent by email to your organization's designated admin user.

### 2. Getting started

* Log in using your credentials at [AlphaGeo Explorer](https://app.alphageo.ai/login).
* Reset your password.

Your password must:

* contain at least 12 characters
* include an uppercase letter, a lowercase letter, a number, and a special character
* not contain your username
* not be too similar to your personal information
* not be a commonly used password
* not be entirely numeric
* not match your last 5 passwords

### 3. Upload your data

Upload your data in our Data Manager to begin asset-level or portfolio-level analysis.

* Refer to our [Data Manager](/alphageo-platform/data-manager.md) user guide for more instructions.&#x20;
* If you are using an API, refer to our guide on [Data APIs](/for-developers/alphageo-data-api.md).

### 4. Navigating our platform

AlphaGeo’s native application, [**AlphaGeo Explorer**](https://app.alphageo.ai/), allows users to analyze existing assets at both asset and portfolio level, and explore new locations for further diligence.

Our [Platform Overview](/alphageo-platform/platform-overview.md) and other related user guides will help your team get started quickly.

If you would like to schedule live demos for your teams, please contact <support@alphageo.ai> or your direct client contact.

Key guides include:

* [Data Manager](/alphageo-platform/data-manager.md)
* [Portfolio Analytics](/alphageo-platform/portfolio-analytics.md)
* [Location Explorer](/alphageo-platform/location-explorer.md)

You can access all **User Guides** at the **bottom-left of our app,** alongside the **Admin Panel**, **Customer Support**, **Feedback & Suggestions**, and **Methodology** tabs.

<figure><img src="/files/miDzpOd9uPyMCHAF4T3n" alt=""><figcaption></figcaption></figure>

### 5. Understanding our data

Use our product and methodology documentation to understand the analytics behind the platform.

Our public product pages provide a high-level overview for users and stakeholders: [AlphaGeo Public Docs](https://www.docs.alphageo.ai).&#x20;

For deeper detail on model logic, inputs, and assumptions, refer to the **Methodology Docs** accessible from within the bottom-left panel of our app.

### 6. For admins: manage your organization

Our [Admin Panel](/alphageo-platform/admin-panel.md) guide explains how designated admins can add team members and manage permissions.

### 7. Support and feedback

The **Customer Support** and **Feedback & Suggestions** options in the bottom-left of our app allow you to contact us directly. You can also email <support@alphageo.ai>.

If you require *urgent* assistance, please email our Client Relations and Tech leads Xiaoyou at <xiaoyou@alphageo.ai> and Mehroz at <mehroz@alphageo.ai>.

### 8. Staying connected

Book your first quarterly consultation, or share feedback at any time by emailing <support@alphageo.ai>.


---

# 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.alphageo.ai/client-onboarding-guide.md?ask=<question>&goal=<endgoal>
```

`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.
