> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/attendant-console/set-up-and-administer/admin-portal.md).
# Configure the admin portal
Configure Attendant Console for Dialogue Cloud admin portal settings.
Use the Attendant Console for Dialogue Cloud admin portal to configure settings that support operator access, mail behavior, connectors, and contact sources.
## Prerequisite
Attendant Console for Dialogue Cloud setup and consent are complete.
{% content-ref url="/pages/yF5PapPWJ5oDjSlyF2EO" %}
[Set up Attendant Console for Dialogue Cloud](/attendant-console/set-up-and-administer/setup.md)
{% endcontent-ref %}
## Open the admin portal
1. Open Attendant Console for Dialogue Cloud.
2. Confirm that the required user is selected.
3. Open the user settings menu.
4. Select **Admin portal**.
Admin portal entry in the Attendant Console user settings menu.
## Admin portal panes
| Pane | Purpose |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Mail | Configure custom SMTP servers, Microsoft 365 mail accounts, server ports, and related mail settings used by Attendant Console. |
| Mail Templates | Create, modify, and delete mail templates. |
| Connectors | Specify user authentication and consent parameters for the Dynamics CRM widget. |
| User privileges | Configure operator access to the admin portal, the **Preferences** menu, personal contacts, group contacts, and widgets. |
| Contact Sources | Create, modify, and delete contact source lists, such as Excel or CSV files stored on OneDrive or SharePoint. |
Mail settings in the Attendant Console admin portal.
{% hint style="info" %}
Admin portal settings can affect multiple operators. Validate changes with a controlled user group before applying them broadly.
{% endhint %}
---
# 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://atlas.anywhere.now/attendant-console/set-up-and-administer/admin-portal.md?ask=&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.
