Hello,
Conflict calendars are typically configured by aggregating multiple schedule sources into a single view. You define calendar layers for **active changes, blackout periods, and maintenance windows**, then overlay them so conflicts are visually apparent. Most implementations use a unified calendar object where each type of schedule is tagged or color‑coded, and rules are set to highlight overlaps. This way, when a user opens the calendar, they can immediately see all active changes alongside blackout and maintenance schedules, making it easier to manage conflicts proactively.
