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

# Administration

## Purpose

Manage platform-level configuration for sources, themes, phones, bots, users, and access control.

## Who this is for

Administrators and supervisors with configuration permissions.

## Prerequisites

* Administrative role in the portal.
* Available integration credentials and business identifiers.

## Before you start

Configure administration assets in this order:

1. [Bots Configuration](/syntphony-messaging-portal/messaging-tools/administration/bots-configuration.md)
2. [Phone Configuration](/syntphony-messaging-portal/messaging-tools/administration/phone-configuration.md) (WhatsApp)
3. [Source Theme](/syntphony-messaging-portal/messaging-tools/administration/source-theme.md) (WebChat branding)
4. [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md)
5. [User Management](/syntphony-messaging-portal/messaging-tools/administration/user-management.md) and [Role Management](/syntphony-messaging-portal/messaging-tools/administration/role-management.md)

## Feature overview

* **Source Configuration:** Connect phone and bot assets into channel sources, or configure **WhatsApp Forward** for external HTTPS endpoints ([WhatsApp Forward source](/syntphony-messaging-portal/messaging-tools/administration/source-configuration/whatsapp-forward-source.md)).
* **Phone Configuration:** Register and manage sender numbers.
* **Bots Configuration:** Configure bot integrations used in message routing.
* **Source Theme:** Configure WebChat widget look and behavior for sources.
* **User Management:** Create and maintain user accounts.
* **Role Management:** Define role-based access.
* **Settings:** Maintain global operational parameters.

## Expected outcome

The portal remains correctly configured, secure, and ready for messaging operations.

## Related pages

* [Dashboard](/syntphony-messaging-portal/dashboard.md)
* [Glossary](/syntphony-messaging-portal/getting-started/glossary.md)
* [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md)
* [WhatsApp Forward source](/syntphony-messaging-portal/messaging-tools/administration/source-configuration/whatsapp-forward-source.md)
* [Phone Configuration](/syntphony-messaging-portal/messaging-tools/administration/phone-configuration.md)
* [Bots Configuration](/syntphony-messaging-portal/messaging-tools/administration/bots-configuration.md)
* [Source Theme](/syntphony-messaging-portal/messaging-tools/administration/source-theme.md)
* [User Management](/syntphony-messaging-portal/messaging-tools/administration/user-management.md)
* [Role Management](/syntphony-messaging-portal/messaging-tools/administration/role-management.md)
* [Settings](/syntphony-messaging-portal/messaging-tools/administration/settings.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-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/administration.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.