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

# Get started with ZBrain XPLR

Follow the step-by-step instructions in this guide to successfully sign up and log in to the ZBrain XPLR platform.

ZBrain XPLR’s multi-tenant SaaS-based architecture introduces a secure, company-specific sign-in experience that ensures each organization (tenant) accesses its own isolated environment.

This guide helps you:

* Get started with ZBrain XPLR- sign in with your corporate credentials
* Access ZBrain XPLR via tenant-specific URLs
* Pick the right authentication path
* Navigate the login and logout flows

### Accessing ZBrain XPLR <a href="#accessing-zbrain-xplr" id="accessing-zbrain-xplr"></a>

#### Tenant-specific login URLs <a href="#tenant-specific-login-urls" id="tenant-specific-login-urls"></a>

Every organization is assigned a unique login URL that automatically applies the correct tenant context. Users are taken directly to their company environment, eliminating the need for repetitive email entry or tenant selection and ensuring a secure, streamlined login experience.

**🔗 URL Format**

{% code lineNumbers="true" %}

```
https://aixplr.thehackettgroup.com/<company-name>/sign-in
```

{% endcode %}

**Example**

If your company is **ABC Corp**, your login URL would be:

{% code lineNumbers="true" %}

```
https://aixplr.thehackettgroup.com/abccorp/sign-in
```

{% endcode %}

**Default tenant: Hackett**

If no company name is specified, users are redirected to the default tenant:

{% code lineNumbers="true" %}

```
https://aixplr.thehackettgroup.com/thehackettgroup/sign-in
```

{% endcode %}

## Sign-in options for ZBrain XPLR <a href="#sign-in-options-for-zbrain-xplr" id="sign-in-options-for-zbrain-xplr"></a>

### Authentication methods overview <a href="#authentication-methods-overview" id="authentication-methods-overview"></a>

ZBrain XPLR supports three primary sign-in methods:

1. **SSO authentication** (Google or Microsoft) - *Recommended for enterprise users*
2. **Email & password** - *Standard credential-based login*
3. **Email-only entry** - *For initial tenant verification and SSO routing*

<figure><img src="https://3781630280-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbuSicczDKTyHzwzicar%2Fuploads%2Fnm2KvTOwRhaKFAqWI8Hl%2Fimage.png?alt=media&amp;token=8caaad93-e7b6-4ee9-991f-2bd728f85bd6" alt=""><figcaption></figcaption></figure>

### Method 1: SSO authentication <a href="#method-1-sso-authentication" id="method-1-sso-authentication"></a>

#### Step 1: Select your SSO provider <a href="#step-1-select-your-sso-provider" id="step-1-select-your-sso-provider"></a>

From your company-specific sign-in page (`https://app.domain.com/<your-company>/signin`), choose your SSO option:

* **Sign in with Google** – for Google Workspace users
* **Sign in with Microsoft** – for Microsoft 365 or Azure AD users

#### Step 2: Redirect to secure login portal <a href="#step-2-redirect-to-secure-login-portal" id="step-2-redirect-to-secure-login-portal"></a>

After clicking your preferred provider, you will be redirected to Google or Microsoft’s secure authentication page

#### Step 3: Enter corporate credentials <a href="#step-3-enter-corporate-credentials" id="step-3-enter-corporate-credentials"></a>

After being redirected to Google or Microsoft’s secure sign-in page:

* You will see a list of your logged-in accounts
* Select your work account associated with your Google Workspace or Microsoft 365 environment
* If you are not already signed in to your provider, you may be prompted to enter your credentials at this stage

If Multi-Factor Authentication (MFA) is enabled, follow your company’s MFA prompts.

#### Step 4: Grant permissions (if prompted) <a href="#step-4-grant-permissions-if-prompted" id="step-4-grant-permissions-if-prompted"></a>

* On your first sign-in, you may be prompted to grant access permissions to ZBrain XPLR
* This step authorizes ZBrain XPLR to securely access your organization’s Google Workspace or Microsoft 365 account, completing the SSO integration and placing you in the correct company.

#### Step 5: Redirect to ZBrain XPLR <a href="#step-5-redirect-to-zbrain-xplr" id="step-5-redirect-to-zbrain-xplr"></a>

* After successful authentication, you will be automatically redirected to your organization’s ZBrain XPLR dashboard.
* You are now signed in and ready to begin using the platform.

### Method 2: Email & password sign-in <a href="#method-2-email-and-password-sign-in" id="method-2-email-and-password-sign-in"></a>

#### Step-by-step process <a href="#step-by-step-process" id="step-by-step-process"></a>

1. **Navigate to your company URL**

{% code lineNumbers="true" %}

```
https://aixplr.thehackettgroup.com/company-name/sign-in
```

{% endcode %}

2. **Enter your credentials**

* **Email address:** Your registered work email
* **Password:** Your ZBrain XPLR password

<figure><img src="https://3781630280-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbuSicczDKTyHzwzicar%2Fuploads%2FU8wYZNcfHb8CWA2QvIQr%2Fimage.png?alt=media&amp;token=d796e154-c1f4-4356-98ef-8cd8aa5badf2" alt=""><figcaption></figcaption></figure>

3. **Click ‘Sign in’**
   * The system validates your credentials
   * Successful authentication redirects you to your workspace

### Method 3: Email-only sign-in <a href="#method-3-email-only-sign-in" id="method-3-email-only-sign-in"></a>

* **Step 1:** Enter your work email address
* **Step 2:** Click ‘Continue’
* **Step 3:** The system validates the email domain.

  * If the domain matches a registered tenant, the workflow proceeds.
  * If not, the user sees “Organization not found.”

  If you are a registered user, the system automatically routes you to the appropriate authentication method based on your organization's configuration.

<figure><img src="https://3781630280-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbuSicczDKTyHzwzicar%2Fuploads%2FT7sS7AfjeuMjnGSwESII%2Fimage.png?alt=media&amp;token=4f1e9a64-2ccf-4173-bcc0-f4f8e7bd6b14" alt=""><figcaption></figcaption></figure>

#### Tenant-aware URL persistence <a href="#tenant-aware-url-persistence" id="tenant-aware-url-persistence"></a>

ZBrain XPLR consistently retains tenant context across navigation, page refreshes, and sessions, ensuring seamless return to the appropriate workspace without additional steps or re-authentication.

#### After logging out behavior <a href="#after-logging-out-behavior" id="after-logging-out-behavior"></a>

When you log out of ZBrain XPLR, the platform ensures you remain within your organization's context. After logging out, you are redirected back to your company-specific sign-in page.

For example, if you originally signed in at "<https://aixplr.thehackettgroup.com/abccorp/sign-in>", you will be redirected. This helps prevent confusion and ensures a smooth re-login experience for users within the same tenant environment.


---

# 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.zbrain.ai/zbrain-documentation/zbrain-xplr/get-started-with-zbrain-xplr.md?ask=<question>&goal=<user_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.
