> For the complete documentation index, see [llms.txt](https://codemash.gitbook.io/codemash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codemash.gitbook.io/codemash/cloud/sms/settings.md).

# Settings

Turn the SMS module off for the project, after seeing everything that will stop.

**Where:** SMS → **Settings** · `/projects/<project>/sms/settings`

The SMS settings screen has one panel, **Disable SMS module**. SMS is not only used by the Campaigns screen — triggers and scheduler tasks send it too, and a campaign may be waiting or sending right now — so the panel first lists everything that depends on SMS and asks you to confirm.

## Before you start

* You need the `sms:manage` permission on the SMS module (for example **Owner** or **Administrator**).
* Check the campaigns that are still waiting or sending in [Campaigns](/codemash/cloud/sms/campaigns.md): every one of them is stopped when the module goes off.

## Steps

1. Open **SMS → Settings**. Read the yellow card **What happens when you disable SMS**: enabled triggers that send via SMS are turned off, scheduled SMS campaign tasks are disabled, and in-flight SMS campaigns are stopped (batches already sending finish; no new batches start).
2. Read the dependency list under the card. It is loaded live and grouped into **Triggers**, **Scheduler tasks** and **In-flight campaigns**; a campaign scheduled for later counts as in flight. When the list is not empty, tick **I understand that disabling SMS will affect the items listed above.** — **Disable module** stays locked until you do.

   <figure><img src="https://712692422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHy372bqsaex2cqS3ikhL%2Fuploads%2Fgit-blob-04e61f7253b73ffa3e00fe612b2ed0da28824c52%2Fsettings-1.png?alt=media" alt="Disable SMS module panel: the What happens when you disable SMS card, In-flight campaigns with Appointment reminder (In-flight campaign), the ticked I understand checkbox and the red Disable module button"><figcaption><p>One scheduled campaign is listed; the checkbox is ticked.</p></figcaption></figure>

   With nothing depending on SMS, the panel shows only the card and the button:

   <figure><img src="https://712692422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHy372bqsaex2cqS3ikhL%2Fuploads%2Fgit-blob-dc8b581cc56b71dabe9034fdeea79a7406455a93%2Fsettings-2.png?alt=media" alt="Disable SMS module panel with no dependencies: the yellow card and the Disable module button"><figcaption><p>Nothing depends on SMS.</p></figcaption></figure>
3. Press the red **Disable module**.

## Result

Cloud goes back to the SMS enable page (**Norbix SMS Notifications** with **ENABLE**), and the SMS menu (Campaigns, Templates, Integrations, Settings) is gone until you enable the module again. Every campaign that was in flight now has the status **Stopped**.

<figure><img src="https://712692422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHy372bqsaex2cqS3ikhL%2Fuploads%2Fgit-blob-46e186cde97a3cd4515984a68ef3cc836d963865%2Fsettings-3.png?alt=media" alt="The Norbix SMS Notifications enable page shown again after Disable module"><figcaption><p>After Disable module: the enable page.</p></figcaption></figure>

Nothing is deleted: templates, integrations and past campaigns stay saved and come back when you press **ENABLE** again (see the [SMS overview](/codemash/cloud/sms.md#enable-the-module)). A stopped campaign does not restart — create it again with **Create new from this** on its [details page](/codemash/cloud/sms/campaigns/details.md). Triggers with an SMS action simply skip the SMS step, so check them before you switch back on. An empty dependency list does not prove that nothing uses SMS: an app that calls the API directly is not listed.

## Change or remove it later

* **Enable again** — open **Sms** in the left menu and press **ENABLE**.
* **No other settings** — this screen has only the disable panel. The API has a settings read ([Get Sms Settings](/codemash/api-reference/notifications/sms/get-sms-settings.md)); it answers an empty `settings` object today.

## Do it from code

```ts
const { dependencies } = await norbix.hub.notifications.getSmsDisableDependencies();
console.log(dependencies); // { triggers: [], schedulerTasks: [], inFlightCampaigns: [ … ], membershipSettings: [] }
if (dependencies.inFlightCampaigns.length === 0) await norbix.hub.notifications.disableSms();

await norbix.hub.notifications.enableSms(); // on again
```

```sh
norbix hub notifications sms disable dependencies get
norbix hub notifications sms disable --yes
norbix hub notifications sms enable
```

The client setup is on the [SMS page](/codemash/cloud/sms.md#use-it-from-code). API: [Get Sms Disable Dependencies](/codemash/api-reference/notifications/sms/get-sms-disable-dependencies.md) · [Disable Sms](/codemash/api-reference/notifications/sms/disable-sms.md) · [Enable Sms](/codemash/api-reference/notifications/sms/enable-sms.md)