> For the complete documentation index, see [llms.txt](https://docs.fenixpyre.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/sign-in-to-the-admin-dashboard.md).

# Sign in to the Admin Dashboard

Use this guide whenever you sign in to the FenixPyre Admin Dashboard at [admin.fenixpyre.com](https://admin.fenixpyre.com) (or your organization's dashboard URL).

Your organization ID and invite details arrive in the invitation email when your tenant is created or when another admin invites you.

## First-time or new browser

1. Open the Admin Dashboard login page.
2. Enter your **organization ID** (for example, the ID from your invite email).
3. Enter your **email address**.
4. Choose how to continue:
   * **Continue with Email** - password sign-in.
   * **Continue with SSO** - when SSO is enabled for your organization.

When you enter your email, FenixPyre detects whether SSO is available for your organization. The options you see depend on the sign-in method configured under Identity & Provisioning.

For Azure AD SSO setup and verification, see [Sign-in to Admin Dashboard with Azure AD](https://docs.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/identity-and-provisioning/saml-single-sign-on-sso-setup/set-up-saml-sso-with-azure/sign-in-to-admin-dashboard-with-azure-ad.md).

## Returning admins - remembered organization and email

After a **successful** admin login, the dashboard remembers the last organization and the email used with it **in this browser** (local storage only - no passwords or tokens).

On your next visit you can:

1. Choose **Continue with \<organization>** as the primary action. *(UI label: confirm exact wording - expected **Continue with \<org name or ID>**.)*
2. Optionally use **Forget** to clear the saved login on a shared computer. *(UI label: confirm - expected **Forget**.)*
3. Or choose **Use another organization** to enter a different organization ID. *(UI label: confirm - expected **Use another organization**.)*

When you continue with the saved organization:

* The email step opens with your last email **prefilled** (you can still edit it).
* Use **Switch organization** on the email step if you need to go back. *(UI label: confirm — expected **Switch organization** / **Back to \<org>**.)*

{% hint style="warning" %}
Saved organization ID and email are visible to anyone using the same browser profile. Use **Forget** on shared machines.
{% endhint %}

### What is and is not saved

| Situation                 | Saved?                                          |
| ------------------------- | ----------------------------------------------- |
| Successful admin login    | Yes — latest organization and that email        |
| Failed or non-admin login | No                                              |
| Logout                    | Session ends; saved organization/email **kept** |
| **Forget**                | Cleared                                         |

Only the **latest** organization and its latest email are remembered — not a list of past tenants.


---

# 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.fenixpyre.com/fenixpyre-for-admins/admin-dashboard/sign-in-to-the-admin-dashboard.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.
