> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/pl/rezerwacja/booking-experiences/remove-sesami-branding.md).

# Usuń branding Sesami

Usuń logo Sesami z kalendarza rezerwacji i e-maili z powiadomieniami, aby zapewnić w pełni spersonalizowane doświadczenie.

{% hint style="info" %}
Dostępne w **Pro** oraz **Premium** .
{% endhint %}

## Co zostanie usunięte

Po usunięciu brandingu Sesami:

* Skrzynka **logo Sesami** zostanie usunięte z kalendarza rezerwacji w witrynie
* Skrzynka **nazwa nadawcy e-maila** zmienia się z „Sesami App” na Twoją **nazwę sklepu** w domyślnych e-mailach z powiadomieniami Sesami

{% hint style="warning" %}
Dotyczy to **tylko domyślnych e-maili Sesami**. E-maile Sesami Flows mają osobne ustawienia nadawcy.
{% endhint %}

## Jak usunąć branding

1. Przejdź do **Sesami > Ustawienia > Ustawienia witryny sklepu**
2. Znajdź **Usuń branding Sesami** opcję
3. Włącz go
4. **Zapisz**

## Powiązane

* [Cennik](/pl/rozpocznij/about-sesami/pricing.md) — porównanie planów
* [E-maile powiadomień](/pl/powiadomienia/notification-emails.md) — ustawienia e-maila
* [Sesami Flows](/pl/automatyzacje/sesami-flows.md) — niestandardowa automatyzacja e-maili


---

# 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://help.sesami.co/pl/rezerwacja/booking-experiences/remove-sesami-branding.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.