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

# Dashboard

AdminX Dashboard is the starting point for 1Kosmos setup—configure session attributes, manage invite emails, connect directories (LDAP), and access profile and analytics

<figure><img src="https://281557795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOTUyFysR7VGBxLPNQgq%2Fuploads%2Fsxq93DwMKidhTdEA2kPr%2Fdashdash%20(1).gif?alt=media&amp;token=9a2d9b86-8b47-48f8-83e4-20198d31bffc" alt="Introduction to Adminx dashboard"><figcaption></figcaption></figure>

The AdminX Dashboard is your starting point for configuring and managing 1Kosmos. From here, you can access guided “Getting started” tiles to set up core capabilities, bring users into the platform, and quickly navigate to your profile and analytics.

**What you can do here**

* Configure **session attributes** used in access and policy decisions
* Manage **invite email templates** for onboarding users
* Connect a **directory (for example, LDAP)** to import and manage users
* Jump to **My Profile** and **Analytics** from the left navigation


---

# 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.1kosmos.com/authentication/admin-portal/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.
