Global lists and settings shared across all configurations
For example, the Block Top-Level Domains list having either a switch to make it global across all configurations; or maybe allow the designation of one configuration to be a "reference configuration" from which others can inherit certain options.
This would be great for deny lists, allow lists, restricted websites apps & games, etc., that cause a lot of redundant work each time you create a new configuration.
3 replies
-
We also need this. We would like the Allow and Deny List to have a global option so you don't have to do it for every profile.
-
Agreed. This would be a quality of life enhancement that would be much appreciated. You can do this type of thing with Control D and its ability to assign two "Profiles" per "Endpoint".
-
This is an amazing idea to have some kind of a "Base" or "Default" profile which other profiles will extend.
However, it would be really great to have a profile hierarchy, when any profile can be based/inherit/extend any another profile:
- Profile A
- Profile B
- Profile C is based on Profile A
- Profile D is based on Profile B
- Profile E is based on Profile C
- etc.
The final configuration can be generated on save and should not be really hard to implement.
Real life use-case:
- Family profile (is a global, for a router, smart TV, etc)
- Kids profile (with more string blocking parameters)
- Adults profile (similar to Family, but with additional blocked/allowed domains)
- Dev profile (for technical devices, for development and more professional work)
To achieve all of that right now, I need to support multiple separate profiles, but with inheritance it would be just a basic profile with some adjustments.
Content aside
-
7
Votes
- 8 days agoLast active
- 3Replies
- 119Views
-
6
Following