> For the complete documentation index, see [llms.txt](https://docs.ecotone.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecotone.tech/messaging/multi-tenancy-support/different-scenarios.md).

# Different Scenarios

Multi-tenancy scenarios and advanced configurations

Once tenant resolution is configured, real systems run into a wider set of needs: tenants on different databases, tenants derived from inbound payloads, propagating tenant context across asynchronous events, isolating dead letters per tenant, and running Console Commands for a chosen tenant. The pages below cover each scenario.

{% content-ref url="/pages/yuBkGcJJEL3mGpjbDuox" %}
[Hooking into Tenant Switch](/messaging/multi-tenancy-support/different-scenarios/hooking-into-tenant-switch.md)
{% endcontent-ref %}

{% content-ref url="/pages/nVN0UOphamdA8GFeansh" %}
[Shared and Multi Database Tenants](/messaging/multi-tenancy-support/different-scenarios/shared-and-multi-database-tenants.md)
{% endcontent-ref %}

{% content-ref url="/pages/Kh0UWhcF9UnoShQAqQh2" %}
[Accessing Current Tenant in Message Handler](/messaging/multi-tenancy-support/different-scenarios/accessing-current-tenant-in-message-handler.md)
{% endcontent-ref %}

{% content-ref url="/pages/5qFpa6lNY4F8KFczwVIM" %}
[Deriving Tenant from Inbound Messages](/messaging/multi-tenancy-support/different-scenarios/deriving-tenant-from-inbound-messages.md)
{% endcontent-ref %}

{% content-ref url="/pages/dLMmOnbPLQOvo3WXn22s" %}
[Events and Tenant Propagation](/messaging/multi-tenancy-support/different-scenarios/events-and-tenant-propagation.md)
{% endcontent-ref %}

{% content-ref url="/pages/qC5JeODUhloC7pnFlqjf" %}
[Multi-Tenant aware Dead Letter](/messaging/multi-tenancy-support/different-scenarios/multi-tenant-aware-dead-letter.md)
{% endcontent-ref %}

{% content-ref url="/pages/WmLddgZm7fTs3WXMdBei" %}
[Tenant-Aware Console Commands](/messaging/multi-tenancy-support/different-scenarios/tenant-aware-console-commands.md)
{% endcontent-ref %}


---

# 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.ecotone.tech/messaging/multi-tenancy-support/different-scenarios.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.