--- title: "What happens when I enable optional monitoring features? (Help Center / Privacy & security / Monitoring)" ai_context: "Use this article for questions about optional RUMvision monitoring features, modular feature enablement, rollout planning, privacy review and how additional diagnostics differ from core Real User Monitoring. It explains that optional capabilities are not enabled automatically, can have different privacy implications, and should be reviewed before production use by technical, privacy, legal, security or compliance teams where appropriate. Relevant for questions about upcoming features, feature activation, property-level configuration, staged rollout, customer control, privacy impact assessments and the distinction between baseline Core Web Vitals monitoring and additional diagnostics." canonical: "https://www.rumvision.com/help-center/privacy-security/monitoring/optional-features-enablement/" --- Breadcrumbs: [Home](https://www.rumvision.com/?format=md) > [Help Center](https://www.rumvision.com/help-center/?format=md) > [Privacy & security](https://www.rumvision.com/help-center/privacy-security/?format=md) > [Monitoring](https://www.rumvision.com/help-center/privacy-security/monitoring/?format=md) > Enabling optional features # What happens when I enable optional monitoring features? RUMvision is modular. That means optional features are not automatically active just because they exist in the platform. You decide which capabilities are enabled for each property, and different features can have different privacy implications. We also believe customers should have time to review new monitoring capabilities before they become available in production. That is why these upcoming features are being announced and documented before they go live. This gives you time to review the changes internally, involve your privacy, legal, security or compliance teams where needed, and decide whether the new functionality fits your own requirements before enabling it. Nothing in this upcoming feature set is intended to be silently switched on for you. The goal is to give you both the technical control and the time needed to make an informed decision. For a typical setup, it helps to think of core Real User Monitoring as the baseline, with additional diagnostics layered on top only when you need them.