From 68b4e18d2bb395ad8e0fc5d8afd15b33abcbc4ef Mon Sep 17 00:00:00 2001 From: GeorgeBark Date: Sun, 14 Jul 2024 13:44:23 +0200 Subject: [PATCH] Update auth_permissions.md to include label_ids This responds to a PR in the core repo. --- docs/auth_permissions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/auth_permissions.md b/docs/auth_permissions.md index e76da25c5a8..32ed6de2584 100644 --- a/docs/auth_permissions.md +++ b/docs/auth_permissions.md @@ -43,9 +43,9 @@ When defining a policy, any dictionary value at any place can be replaced with ` ## Entities -Entity permissions can be set on a per entity and per domain basis using the subcategories `entity_ids`, `device_ids`, `area_ids` and `domains`. You can either grant all access by setting the value to `True`, or you can specify each entity individually using the "read", "control", "edit" permissions. +Entity permissions can be set on a per entity and per domain basis using the subcategories `entity_ids`, `device_ids`, `area_ids`, `label_ids` and `domains`. You can either grant all access by setting the value to `True`, or you can specify each entity individually using the "read", "control", "edit" permissions. -The system will return the first matching result, based on the order: `entity_ids`, `device_ids`, `area_ids`, `domains`, `all`. +The system will return the first matching result, based on the order: `entity_ids`, `device_ids`, `area_ids`, `label_ids`, `domains`, `all`. ```json {