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

# Settings

Turn the Database module off for a project, or on again — no data is deleted.

**Where:** Database → Settings · `/projects/<project>/db/settings`

Database **Settings** holds one action: turning the Database module off for this project. The settings of one collection (description, soft delete, records with an owner, AI embed) are on that collection's [schema Settings tab](/codemash/cloud/database/collections/edit-schema.md#change-or-remove-it-later).

## Before you start

* You need a project role that can manage modules (`database:manage` on `database:module:all`), for example **Administrator**.
* Disabling turns the Database screens off for everyone in the project until the module is enabled again.

## Steps

1. Open **Database → Settings**. The panel **Disable the Database module** says that your schemas, taxonomies, records and database integrations are kept.

   <figure><img src="https://712692422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHy372bqsaex2cqS3ikhL%2Fuploads%2Fgit-blob-5fc38fea5c59fbfcd10f91538d29a0a48a3c1acf%2Fsettings-1.png?alt=media" alt="Database Settings: the panel Disable the Database module — You can disable the Database module for this project. Your schemas, taxonomies, records and database integrations are kept: enable the module again to use them. A red Disable module button"><figcaption><p>Database → Settings.</p></figcaption></figure>
2. Press **Disable module**. The dialog **Disable the Database module?** says the Database screens are turned off until you enable the module again, and that no data is deleted.

   <figure><img src="https://712692422-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHy372bqsaex2cqS3ikhL%2Fuploads%2Fgit-blob-21c85c45ba23411952f684a723df5dad1942c825%2Fsettings-2.png?alt=media" alt="Dialog Disable the Database module?: The Database screens are turned off for this project until you enable the module again. No data is deleted. Cancel and Disable module"><figcaption><p>The confirmation dialog.</p></figcaption></figure>
3. Press **Disable module** in the dialog, or **Cancel** to keep the module on. While it works, the panel says **Disabling the module…**; you can leave the page open — it moves on by itself.

## Result

Cloud opens the Database enable page (**Norbix Database** with **ENABLE**), the same page a project sees before the module is first turned on — see [Database → Enable the module](/codemash/cloud/database.md#enable-the-module). If something went wrong, the panel says **The module was not disabled** with the reason.

* No data is deleted: schemas, taxonomies, records, aggregates, triggers and integrations are kept.
* A managed Atlas Flex cluster behind an integration keeps running while the module is off. To remove it, [delete the integration](/codemash/cloud/integrations/disable.md) first.

## Change or remove it later

* **Enable again** — press **ENABLE** on the Database page. Cloud opens **Database → Collections**, with all your collections, records and integrations still there.

## Do it from code

```ts
await norbix.hub.database.disableDatabase();
await norbix.hub.database.enableDatabase();
```

```sh
norbix hub database enable
```

Enable and disable are `PUT` requests. The client setup is on the [Database page](/codemash/cloud/database.md#use-it-from-code). API: [Disable Database](/codemash/api-reference/database/module/disable-database.md) · [Enable Database](/codemash/api-reference/database/module/enable-database.md)