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

# Dashboard

## Sign in

Open your Sendman Admin Portal at `https://YOURNAME.sendman.com` and sign in with one of the identity providers enabled for your instance (see [Permissions](/admin-portal/settings/permissions.md)). Only accounts listed as administrators or viewers can sign in.

## Navigation

<figure><img src="https://1641814212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EVg4twS3gtObqtkynsm%2Fuploads%2Fgit-blob-76886beb032814a0aaa0d10ef0bfad5bbe99c724%2Fportal-dashboard.png?alt=media" alt="Sendman Admin Portal dashboard"><figcaption></figcaption></figure>

The menu on the left gives access to all areas of the portal:

| Menu group   | Pages                                                                                                                                                                                                                                    |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Sendman**  | [IP Allow List](/admin-portal/sendman/ip-allow-list.md), [Authorization Policies](/admin-portal/sendman/authorization-policies.md), [SMTP Credentials](/admin-portal/sendman/smtp-credentials.md)                                        |
| **Insights** | [Overview](/admin-portal/insights/overview.md), [Logs](/admin-portal/insights/logs.md), [Uptime](/admin-portal/insights/uptime.md)                                                                                                       |
| **Settings** | [Permissions](/admin-portal/settings/permissions.md), [Network Connections](/admin-portal/settings/network-connections.md), [SMTP Client](/admin-portal/settings/smtp-client.md), [SMTP Backend](/admin-portal/settings/smtp-backend.md) |

The top of the menu shows the name of your instance (**Tenant**). Hover over the Sendman logo to see your user name, your role and the Sendman version.

## Other controls

Click on your name in the top right corner to open the user menu.

### Dark Mode

Choose **Dark mode** or **Light mode** to switch the theme of the portal.

### Language

The Sendman Admin Portal is available in English, German, Spanish, French, Japanese and Portuguese. Select the language in the user menu.

### Sign out

Choose **Sign out** to end your session.

### Documentation

The **Documentation** link at the bottom of the menu opens this documentation.

## Roles

What you can do in the portal depends on your role:

| Role              | Permissions                                                                                      |
| ----------------- | ------------------------------------------------------------------------------------------------ |
| **Administrator** | View and change all settings, manage permissions and API access tokens                           |
| **Viewer**        | View all settings. Pages show the notice *You have view-only access* and offer no edit controls. |

Roles are assigned under [Permissions](/admin-portal/settings/permissions.md).


---

# 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.sendman.com/admin-portal/home.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.
