This page explains what modules are. It is useful to know, because modules determine what you see on screen and where you find the documentation for it.
What a module adds
A module adds a subject to the base program. Examples are songs, name plates, subtitles, the import of presentations, video services, control of a vision mixer, moving backgrounds, a logo on the picture, automation rules, and the songs and people of a publisher. A module brings its own buttons, cue types, windows and designs.
What this means at the desk
You never see something that you cannot use. There are no greyed-out buttons, no menu items that need something else, and no settings pages for a function that is missing.
Two installations can look different. A colleague’s screenshot may show a button that you do not have. This says nothing about the size of a licence, because it only shows which components are installed. You can check this under Settings → Modules.
A module that you switch off removes its parts from the interface. They are not disabled, but not present at all. When you switch the module on again, everything returns.
A module with a problem does not stop the broadcast. The cue list, the outputs and the show continue, and you lose only what the module provided.
A module that waits for something slow, such as a network drive or a service that does not respond, makes the program start more slowly. The line Loading modules… on the loading screen shows that the program is waiting at that point.
What remains yours
Your own templates, and the designer in which you make them, belong to the program and not to a module. So you do not lose your own work when you switch modules on or off.
Where each module is documented
Each module has its own part of this manual, and the page all modules lists them.