# Official shipped action groups
**URL:** https://forum.search-guard.com/t/official-shipped-action-groups/1740
**Category:** Search Guard
**Created:** [January 17, 2020, 9:51am UTC](https://forum.search-guard.com/t/official-shipped-action-groups/1740 "2020-01-17T09:51:48Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@faxmodem](https://forum.search-guard.com/u/faxmodem)
#### Post date: [January 17, 2020, 9:51am UTC](https://forum.search-guard.com/t/official-shipped-action-groups/1740/1 "2020-01-17T09:51:48Z")
It’s not clear to me if the shipped action groups in the sgconfig file need to be explicitly uploaded.
In any case, it would be much simpler from a user perspective to have those hardcoded in the searchguard plugin, so that when something changes in Elasticsearch permissions, search-guard would implement the changes (e.g. SEARCH would be adapted) and the user wouldn’t have to update his/her action groups.
---
### Author:  [@faxmodem](https://forum.search-guard.com/u/faxmodem)
#### Post date: [January 21, 2020, 10:08am UTC](https://forum.search-guard.com/t/official-shipped-action-groups/1740/2 "2020-01-21T10:08:45Z")
I guess this answers my question, excerpt from [Upgrading from 6.x to 7.x | Security for Elasticsearch | Search Guard](https://docs.search-guard.com/latest/upgrading-6-7) :
> **Migrating to the new built-in roles**
> Search Guard 6 shipped with a couple of demo users, roles and action groups. In Search Guard 7, some of them are now built-in and cannot be changed
---
### Author:  [@hsaly](https://forum.search-guard.com/u/hsaly)
#### Post date: [January 27, 2020, 1:16pm UTC](https://forum.search-guard.com/t/official-shipped-action-groups/1740/3 "2020-01-27T13:16:02Z")