This page explains what modules are, because they decide what you see on screen and where you find the documentation for it.
What a module adds
A module adds a subject the base program does not have: songs, name plates, subtitles, presentation import, video services, switcher control, moving backgrounds, a logo on the picture, automation rules, a publisher’s songs and people. Its buttons, its cue types, its windows and its designs all come with it.
What that means at the desk
You never see something you cannot use. No greyed-out button, no menu entry that turns out to need something else, no settings page for a feature that is not there.
Two installations can look genuinely different. A colleague’s screenshot may show a button you do not have, and that says nothing about who has the bigger licence — it says which components were installed. Check Settings → Modules.
A module you switch off takes its parts with it. Not disabled: gone. Switch it back on and everything returns as it was.
A module that gets into trouble does not stop the broadcast. The cue list, the outputs and the show keep running; you lose what that module provided.
A module that hangs on something slow — a network drive, a service that does not answer — shows up as a start that takes longer than usual. The Loading modules… line on the loading screen is where it waits.
What stays yours
Your own templates and the designer you make them in belong to the program, not to a module. Switching modules does not cost you your own work.
Where each module is documented
Each module has its own part of this manual — all modules lists them.