# Default group for new block/whitelists

**URL:** <https://discourse.pi-hole.net/t/default-group-for-new-block-whitelists/44694>\
**Category:** General\
**Created:** [February 22, 2021, 4:10pm UTC](https://discourse.pi-hole.net/t/default-group-for-new-block-whitelists/44694 "2021-02-22T16:10:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![emroch](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/emroch/32/23808_2.png) [@emroch](https://discourse.pi-hole.net/u/emroch)\
**Post date:** [February 22, 2021, 4:10pm UTC](https://discourse.pi-hole.net/t/default-group-for-new-block-whitelists/44694/1 "2021-02-22T16:10:14Z")

</div>

So I know that we have the ability to define multiple client groups and change the adlists/blocklists/whitelists for each one. I also know that clients are assigned to "Default" automatically unless you configure them for a different group. New lists (ad/block/white) are also assigned to the default group unless you change it.

I propose a feature whereby you may select an arbitrary default group, not only for new clients but also for new lists. The ability to choose the default client group is not strictly necessary, but would not be difficult to query the list of groups and present a choice (and probably display something like "(client default)" next to its name in the group management pane.

Feature motivation:

My default group has very minimal blocking. Basically just stevenblack + some broad whitelists since my visiting family members would complain about Google search ads etc being broken. Rather than remembering to configure each guest device that joins the network, I just made the default group as non-breaking as possible. This means my most used devices are on another group though, so anytime I need to allow/block a domain on my device, it takes an extra step to go assign the group correctly.  
If I could instead configure it such that changes to exact/regex blocklists and whitelists apply to certain groups by default, it would remove a step. It would also make many external tools for adding domains work properly since most (all?) just add to the default group.

---

<div class="post-metadata">

**Author:** ![yubiuser](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/yubiuser/32/12100_2.png) [@yubiuser](https://discourse.pi-hole.net/u/yubiuser)\
**Post date:** [February 22, 2021, 6:30pm UTC](https://discourse.pi-hole.net/t/default-group-for-new-block-whitelists/44694/2 "2021-02-22T18:30:22Z")

</div>

_I converted this to a feature request_

You can do this already, but just not from the GUI. You need to change the triggers of the `gravity.db` which assigned new adlists/domains to Group ID 0.

See this topic for more info and also the warning by **DL6ER**

> [@Group Management question](https://discourse.pi-hole.net/t/group-management-question/32062):
>
> Hello, I recently started using Pi-Hole and upgraded to 5.0 a few days ago. The group management feature is great but I have a question regarding that. Maybe I am missing something. Say I have two groups: Unclassified (Default Group, I guess) My Group (User created) Now, every time I add an ad list or whitelist/blacklist a domain, I have to go and apply that to both these groups since by default it's only applied to the default group. 99% of the time, when I make any of these changes (add…

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [March 15, 2021, 6:30pm UTC](https://discourse.pi-hole.net/t/default-group-for-new-block-whitelists/44694/3 "2021-03-15T18:30:32Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.