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

# Settings

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

**Where:** Push → **Settings** · `/projects/<project>/push/settings`

The Push settings screen has one panel, **Disable push notifications module**. Push 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 Push and asks you to confirm.

## Before you start

* You need a project role that can manage modules (for example **Owner** or **Administrator**).
* Check the campaigns that are still waiting or sending in [Campaigns](/codemash/cloud/push/campaigns.md): every one of them is stopped when the module goes off.

## Steps

1. Open **Push → Settings**. Read the yellow card **What happens when you disable Push**: enabled triggers that send via Push are turned off, scheduled Push campaign tasks are disabled, and in-flight Push 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 Push 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-b11e609c5d22219c0a1386d8a226706decf4ba80%2Fsettings-1.png?alt=media" alt="Disable push notifications module panel: the What happens when you disable Push card, In-flight campaigns with Weekend sale (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 Push, 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-5e6a06099e5fad72c4abf11c9f7405d938b54170%2Fsettings-3.png?alt=media" alt="Disable push notifications module panel with no dependencies: the yellow card and the Disable module button"><figcaption><p>Nothing depends on Push.</p></figcaption></figure>
3. Press the red **Disable module**.

## Result

Cloud goes back to the Push enable page (**Norbix Push Notifications** with **ENABLE**), and the Push menu is gone until you enable the module again. Every campaign that was in flight now has the status **Stopped** — the `Weekend sale` campaign above was scheduled for 4 December and is never sent.

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

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

## Change or remove it later

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

## Do it from code

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

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

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

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