> 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/account-management/enabling-or-disabling-sesami.md).

# Enabling or Disabling Sesami

You can quickly show or hide the Sesami booking button on your online store without uninstalling the app.

## How to Enable or Disable

1. Go to **Sesami > Settings > Sesami Status**
2. Toggle Sesami **on** or **off**
3. **Save**

When disabled, the Sesami booking button disappears from your product pages. When re-enabled, it reappears.

{% hint style="warning" %}
**Disabling Sesami does not cancel your subscription.** You'll continue to be billed. To cancel billing, see [Cancel Your Subscription](https://help.sesami.co/account-management/billing/cancel-subscription.md).
{% endhint %}

## When to Use This

* **Temporarily hide bookings** — during store maintenance, inventory updates, or seasonal changes
* **Test before going live** — disable Sesami while configuring, then enable when ready
* **Quick toggle** — turn off bookings without removing any configuration

All your services, resources, availability, and settings remain intact while Sesami is disabled.

## Related

* [Cancel Your Subscription](https://help.sesami.co/account-management/billing/cancel-subscription.md) — fully remove Sesami and cancel billing
* [Pause or Freeze the Subscription](https://help.sesami.co/account-management/billing/pause-or-freeze-subscription.md) — pause billing for seasonal businesses


---

# 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/account-management/enabling-or-disabling-sesami.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.
