From 0dacdaf8cbf3277d47604cbbabe667efff8569bf Mon Sep 17 00:00:00 2001
From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com>
Date: Mon, 25 May 2026 06:37:38 -0500
Subject: [PATCH] tweak

---
 docs/docs/configuration/profiles.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/docs/configuration/profiles.md b/docs/docs/configuration/profiles.md
index 87fd329384..a7b3b2f50d 100644
--- a/docs/docs/configuration/profiles.md
+++ b/docs/docs/configuration/profiles.md
@@ -216,6 +216,8 @@ In this example:
 
 No. Profiles are pure overrides. Every zone and mask defined under a profile must reference an entry that already exists on the base camera config. Configurations that introduce profile-only zones or masks are rejected at startup.
 
+If you want a zone or mask to be active only under a specific profile, define it on the base config with `enabled: false`, then enable it in that profile's overrides.
+
 ### How do I revert a profile zone or mask override back to the base configuration?
 
 Delete the override. In the Frigate UI, edit the profile and use the "Revert override" action (the trash can icon) on the zone or mask. The base entry is left untouched, and once the override is removed the profile inherits the base values for that zone or mask.