---
title: How to switch parts of Tideswell on and off
url: https://tideswell.xyz/docs/workspace-admin/modules
description: Modules decide which parts of the product exist for your workspace, with a preview of exactly what stops before anything changes.
---

> Documentation index: fetch https://tideswell.xyz/llms.txt to discover every page before exploring further.

# How to switch parts of Tideswell on and off



**Settings › Modules** decides which parts of Tideswell your workspace has. Switching one off
removes it from the sidebar and makes its pages unreachable, and never deletes anything inside
it.

## What is an operating model? [#what-is-an-operating-model]

Three cards, **Reseller**, **Brand owner** and **Vertically integrated**, plus an **Also sells
wholesale** switch.

Together they answer two questions: how you get product, and whether you sell wholesale. Your
answers set sensible module defaults, so a reseller does not start with a production-orders menu.

Changing either shows a preview first, listing what switches on, what switches off, what
background work stops, and which of your own choices are kept. Read that dialog rather than
clicking through it.

## Does a model change override my own switches? [#does-a-model-change-override-my-own-switches]

No. **A module you switched by hand keeps winning** over a later model change, and the dialog
says so.

That is usually what you want and occasionally confusing. **Reset to model defaults** throws away
your own changes and goes back to what the model says, for a clean slate.

## How are modules grouped? [#how-are-modules-grouped]

Into **Core**, **Commerce**, **Supply**, **Manufacturing** and **Wholesale**, each showing how
many are on.

Row badges tell you where each setting came from: **Always on**, **From your model**, **On by
default**, or **Changed**.

**Always on** marks the structural modules, Home, Chat and Tasks. Those cannot be switched off in
any workspace.

## What actually happens when you switch one off? [#what-actually-happens-when-you-switch-one-off]

It disappears from the sidebar and its pages become genuinely unreachable, including from an old
bookmark. You get a not-found page rather than a redirect.

Nothing inside is deleted. Switching it back on returns everything as it was.

Its background work stops too. Turning off Automations stops every automation in the workspace
including task due-date reminders, while background data sync keeps running. The dialog names
what stops in each case.

## What should you switch off? [#what-should-you-switch-off]

The parts you genuinely do not use, because an unused module is a menu item that makes the
product harder to learn.

A brand that does not sell wholesale should not carry a Wholesale row. A workspace with no
Shopify store should not carry Store.

What you should **not** do is switch something off to hide it from certain people. That is a
permission question, per <Ref to="workspace-admin/permissions" />: a module is off for
everybody or on for everybody.

## Why is a module listed with no screen? [#why-is-a-module-listed-with-no-screen]

Several are listed so you can see the shape of the product, and have no screen yet: Shipments,
Inventory, Forecasting, Assortment planning, Samples, Production orders, Bills of materials,
Price lists and Allocation.

They can be toggled and nothing appears. Note that the **Inventory** here is the top-level
module: the stock screens you actually use live under Store, per <Ref to="inventory" />.

**Approvals** has no toggle of its own, because it rides the Purchase orders module.

## What breaks when somebody switches one off? [#what-breaks-when-somebody-switches-one-off]

Anything that depended on it, quietly and immediately. That is worth saying out loud before you
change one in a busy workspace.

An automation whose module is off records a skipped run saying its automations are dormant, per
<Ref to="automations/check-it-worked" />. An analyst digest button whose module is off is removed
from the home page.

When somebody reports a missing button or a dead bookmark, this screen is the first place to
look. See <Ref to="troubleshooting/missing-button" />.
