# Configuring Screens and Actions Groups

Screen and action groups can be configured on the ["Installer->Screens & Actions" step](screensAndActions.md).

![](../images/ui/beans_action_group.png)

Actions and screens can be grouped in the tree of installer elements. Groups of the same types can be nested, meaning that you can put a screen group into a screen group or an action group into an action group.

You can nest as many levels of groups as you wish. Next to the label of the screen or action group in the tree of installer elements the number of all contained screens or actions is shown in bold where elements in nested groups are counted as well.

Grouping offers the following benefits:

- **Organization** — If you have many screens or actions, groups emphasize which elements belong together. You can add a common comment to the group.
- **Common condition** — Groups have a "Condition expression" property that allows you to skip the group with a common condition instead of having to repeat the condition for each contained element.
- **Single link target** — If you want to reuse a set of adjacent screens or actions in a different part of your project, you can put them in a group and add a single link to that group instead of linking to each element separately.
- **Looping** — A group has a "Loop expression" property that allows you to execute the group repeatedly until the loop expression returns `false`.
- **Jump targets (screen groups only)** — When you jump to a screen programmatically with `context.gotoScreen(...)`, it is more maintainable to jump to a group instead of to a single screen. You can think of the group as a label in this case.

### Properties of screen and action groups

The common properties of screen and action groups are:

_See `reference/beans/` for the bean catalog._

In addition, action groups have the following properties:

_See `reference/beans/` for the bean catalog._
