# Kill switches and modules

The kill switches staff can turn off for an org, and the modules an org can switch on or off.

EasyCode staff can turn a feature off for one org or for every org at once. While a switch is off, the api routes behind it
answer _503_. The table is generated from the switches the api knows.

| Switch | Id | What turning it off does |
| --- | --- | --- |
| Design boards | `board` | Live boards close; boards open read-only. |
| Browser | `browser` | The desktop app stops opening its built-in browser for this org. |
| Design system | `design` | Design system pages and their routes close; products and their Design system tab stay. |
| Documents | `documents` | Task documents stop answering, in the app and in harness tools. |
| Knowledge runs | `knowledge` | Tasks can no longer be claimed or send results; setup and review still work. |
| Library publishing | `library_publish` | Library changes can no longer be published; user-scope assets still save. |
| Live editing | `live_editing` | Live editing closes; documents open read-only at their last version. |
| Pick-up | `pickup` | A session can no longer be picked up on another machine. |
| Workflow runs | `runs` | Workflow runs can no longer start or move on; the board still works. |
| Studio | `studio` | Artifacts can no longer be opened, published or changed; frames already loaded lapse within minutes. |
| Sync | `sync` | Runners stop sending sessions to the cloud. |
| Trackers | `trackers` | Jira and Linear stop syncing, and their jobs stop; tasks already linked stay as they are. |
| Uploads | `uploads` | Session content is no longer stored. |
| Voice | `voice` | New voice takes are refused; takes already made still play. |

## Modules

A module is a part of EasyCode an org is entitled to, such as `studio`, `design` or `browser`. Staff set an org's modules
in the staff console. A route that belongs to a module answers _404_ to an org without it, so the feature isn't there at
all, while a kill switch turns a feature off for orgs that have it.

Some modules count only together. `studio` is in force only beside `sessions`, and `voice` is no module of its own: an org
has it where `studio` stands beside `integrations`.
