> 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/settings.md).

# Settings

## Purpose

Maintain **tenant-level** preferences and operational defaults for the Messaging Portal.

## Who this is for

Administrators with permission to change organization-wide portal behavior.

## Prerequisites

* Administrator role.
* Documented organizational policies for defaults and feature usage.

{% hint style="warning" %}
This page documents **Messaging Portal** settings only. Live Agent Console settings (chat capacity, quick responses, conversation tags, and similar agent-workspace controls) are configured in the Console, not here.
{% endhint %}

## Steps

1. Open **Administration** and go to **Settings**.
2. Review current tenant defaults and feature switches.
3. Update values according to organizational policy.
4. Save changes and confirm impacted modules behave as expected (for example, default sender or date range behavior).
5. Communicate changes to supervisors and operators when defaults affect daily workflows.

## Validation

* Saved settings persist after refresh.
* Dependent modules reflect new defaults without conflicting overrides in [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md).

## Expected outcome

Platform behavior remains aligned with organizational policies across portal modules.

## Related pages

* [Administration](/syntphony-messaging-portal/messaging-tools/administration.md)
* [Widget Theme](https://github.com/bmcntt/syntphony-messaging-portal-docs/blob/main/messaging-tools/administration/widget-theme.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/settings.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.