> 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/platform-administration/readme.md).

# Platform administration

Entry point for Dialogue Cloud administration topics in Atlas.

Use this section to provision contact-center resources and administer applications after the environment prerequisites and customer onboarding are complete.

## Where this section starts

[Start](https://atlas.anywhere.now/) owns prerequisites, deployment choices, and customer onboarding. Platform administration owns repeatable provisioning and ongoing application administration.

## Choose a task

Work through the first two routes in order when you are building a new contact center. Return directly to the relevant administration route for later changes.

| If you need to...                                                              | Go to...                                                                                   |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ |
| Provision or manage Services and Contact Centers                               | [Provisioning](/platform-administration/provisioning/provisioning.md)                      |
| Add people, queues, routing, reusable assets, and callflows after provisioning | [Contact center configuration](https://atlas.anywhere.now/contact-center-configuration/)   |
| Access Snapper, Wallboard, or Web Wallboard documentation                      | [Maintenance-mode applications](#maintenance-mode-applications)                            |
| Set up the Power BI Template                                                   | [Reporting administration](/platform-administration/reporting-administration/reporting.md) |

## Maintenance-mode applications

Snapper, Wallboard, and Web Wallboard are maintenance-mode applications. Existing deployments remain supported for maintenance and critical/security fixes. They no longer receive new feature development and are unavailable for Dialogue Cloud Neo (Unify). For Unify, use [Dialogue Workspace](/use/monitor-and-report/dialogue-workspace.md).

* [Snapper](/platform-administration/maintenance-mode-applications/snapper.md)
* [Wallboard](/platform-administration/maintenance-mode-applications/wallboard.md)
* [Web Wallboard](/platform-administration/maintenance-mode-applications/request-and-secure-web-wallboard.md)

## Continue the journey

After provisioning and the core contact-center build:

* set up and administer the operator console in [Attendant Console](https://atlas.anywhere.now/attendant-console/)
* connect customer entry points and external systems in [Channels & integrations](https://atlas.anywhere.now/channels-integrations/)
* validate daily workflows in [Use](https://atlas.anywhere.now/use/)
* monitor, maintain, diagnose, or escalate in [Operate](https://atlas.anywhere.now/operate/)
* check product definitions and technical details in [Product reference](https://atlas.anywhere.now/product-reference/)


---

# 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/platform-administration/readme.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.