jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-05-08 12:08:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update auth_permissions.md (#195)

Browse Source
This commit is contained in:
Paulus Schoutsen 2019-03-11 11:02:40 -07:00 committed by GitHub
parent 9fd4219332
commit 1e16612d56
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/auth_permissions.md
View File

@ -35,18 +35,21 @@ 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` and `domains`. Granting access to an entity means a user will be able to read the state and control it.
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.
If an entity is specified in both the `entity_ids` and `domains` subcategory, the `entity_ids` result will be used, unless it is `None`. In the following example, the user will have access to all light entities except for `light.kitchen`.
The system will return the first matching result, based on the order: `entity_ids`, `device_ids`, `area_ids`, `domains`, `all`.
```python
```json
{
"entities": {
"domains": {
"light": True
"switch": true
},
"entity_ids": {
"light.kitchen": False
"light.kitchen": {
"read": true,
"control": true
}
}
}
}