# Get started with Supergroups

> A Supergroup is a group created dynamically based on attributes in Rippling. Members update automatically when those attributes change.

## What is a Supergroup?

A Supergroup is a group created dynamically based on shared attributes in Rippling. Instead of including individual people by name, you can make a Supergroup based on attributes such as department, location, tenure, employment status, or course certification status, and people who share those attributes will automatically be included in the group.

The members of a Supergroup are updated automatically when the attributes in Rippling change. Say an employee gets promoted, switches departments, or leaves the company, that employee will automatically be included in Supergroups that match their new attributes and excluded from Supergroups where their attributes no longer match.

Supergroups let you utilize your employee data in Rippling to automate access across the system, saving time, eliminating manual errors, and ensuring people always have what they need when they need it.

Anywhere in Rippling that you see the Include/Except box, you can set up a Supergroup.

You can list and inspect saved groups with [Get started with the Supergroups API](https://developer.rippling.com/documentation/rest-api/guides/supergroups-getting-started).

## Attributes you can use when defining Supergroups

Any attribute in the Rippling data model can be used to define a Supergroup. Here are just a few examples of the attributes you can use:

-   Department, team, or level
-   Work location
-   Country, state, or city of residence
-   Employment type or status
-   Compensation details
-   Whether or not someone is a manager or admin
-   Whether or not someone is currently on leave
-   Someone’s pay frequency
-   Someone’s work relationships, such as who their peers are, who their manager is, or their work relationship to a specific person
-   Custom fields you’ve added to Rippling

Supergroups can be as simple or as complicated as you need them to be to target the right people. For example, a Supergroup can include everyone in the Marketing department, or everyone in the Marketing department who is on the Events team except for 1099 contractors.

When using an employee's attributes to create a Supergroup, you must have access to an attribute for the scope of the entire company to use it. For more information, see [Permissions for data in Rippling](https://developer.rippling.com/documentation/rippling-platform/data-model/permissions).

## Use cases for Supergroups

Here are a few more examples of how you can use Supergroups to automate and optimize group management in Rippling.

-   Set up an automation that sends a scheduled report to the members of the Sales department. Even if the actual members of the Sales department change, Rippling will continue to send the report to the right people without the need to modify the automation.
-   Create a permission profile that’s assigned to all of your Director-level employees. When an employee is promoted to Director, they’ll automatically inherit the permission profile that gives them the access they need.
-   Set up a data access policy for Zendesk that lets managers in the Customer Service department use data from your Zendesk tickets to trigger automations in Rippling. When Customer Service agents are promoted to manager, they’ll automatically get access to use Zendesk data in automations.
-   Set a policy that gives access to the AWS Admin group only to engineers of level 6 or 7 who have at least one year of tenure, use a security key to sign in to Rippling, and have an HIPAA certification. When engineers' attributes change to meet these criteria, they're automatically added to the group.

## Methods for creating Supergroups

There are two different ways you can create Supergroups:

-   You can **save** them in the Saved Supergroups app and then use them throughout Rippling wherever the Supergroups box is available. This is a good option if you want to ensure your groups are managed consistently across Rippling.
-   You can create a Supergroup **on the fly** anywhere you see the Supergroups box. For example, when setting up an automation that sends an email, you can create a Supergroup right within the automation to define the recipients of the email. This is a good option for one-off groups that don’t need to be reused or regularly audited.

* * *

## Define a Supergroup

When setting up a Supergroup, you’ll define exactly what you want to include and, if relevant, what you want to exclude.

### Using the include/except box

Add the people or groups you want to include to the **Include** box. Anything you add next to **Except** will be excluded. For example, you could set up a Supergroup that includes everyone _except_ contractors and temporary employees.

When you click in the Supergroups box, a menu appears with options for defining the group. You can select from work relationships, employee attributes, or predefined categories such as all managers or all admins.

### Combine attributes using unions and intersections

You can use any combination of the available options when defining a Supergroup. When you combine them, you can use the **union** of the data to create a larger, inclusive group or the **intersection** of the data to create a smaller, more refined group.

#### Use a union to create an inclusive group

The **union** of two data sets is the combination of everything that’s in the two sets. This will create a broad group that includes everything that includes any of the attributes you define. To create a union, do not add an AND operator to connect the groups.

For example, let’s say you add employees in the last pay run (30 employees) and employees whose annual compensation is greater than $50,000 (13 employees).

A total of 43 people will be in the group:

-   All 30 employees in the last pay run.
-   All 13 employees whose compensation is greater than $50,000.

#### Use an intersection to narrow the group based on commonalities

The **intersection** of two data sets is ONLY the elements that are in both sets. This will create a smaller, more refined group that includes only things that share the attributes you define. To create an intersection, hover over the data element and add an AND operator to connect the groups.

To continue the example, let’s say you add employees in the last pay run (30 employees), add an AND operator, and add employees whose annual compensation is greater than $50,000 (13 employees).

Only 10 employees with annual compensation over $50,000 were ALSO included in the last pay run. So in this instance, only those 10 employees will be in the group.

#### Use unions and intersections together in a group

You can use both unions and intersections in the same group. For example, let’s say you want to create an automation that sends an email to an employee’s manager and an admin in the HR department when an employee has been with the company for more than 90 days. In this case, you’d set up your Supergroup to include:

-   The employee’s manager. Choose **The employee: their manager**.
-   The HR department AND all admins. Add **Human Resources Department**, hover over it and click **\+ AND**, then add **All Admins**. This creates an intersection to include only people who are both an admin AND in the HR department.

As a result, these people will be in the group:

-   The employee’s manager.
-   All admins who are in the HR department.

If you do not use the AND connector, the group includes the employee’s manager, all members of the HR department, and all admins.

> **Note:**
> For automations that create an email or Slack notification, if an employee happens to fall into multiple groups, they’ll only be notified once.

### Filter by employment status

By default, only employees in certain statuses are included in Supergroups. In some places, you can customize this to include employees in different statuses.

### Filter by legal entity

By default, Supergroups include people across all of your legal entities. To filter a group to specific entities, click **Applies to: All entities** at the top of the box and then select the desired entities. Unchecking an entity excludes it from the Supergroup.

You can also filter based on the legal entity to which a specific person in the group belongs:

1.  Add a specific individual to the group.
2.  Hover over the person’s name and select **Relationship**.
3.  In the field **Select relationship to employee**, select _Entity: Everyone in the same legal entity as the employee_.
4.  Click **Insert**.

### Include employees based on their relationships to specific people

You can also include employees based on their relative relationships to a specific person. For example, you can add a specific person and then say you want to include all of that person's peers as part of the Supergroup.

### Include specific employees

If you need to, you can choose one or more specific employees instead of defining a Supergroup. Scroll down to the option to **Select a specific employee** and search by name.

Keep in mind that when you choose a specific employee, if things change, you may need to modify the group. For example, if you choose an employee named Elana Baumbach as the recipient of an automation email action, but Elana transfers to a different department that shouldn’t be involved in that automation, you’ll need to update the automation to change the recipient to someone else. We recommend that you use the attributes available in Supergroups whenever possible because it will make it much less likely you’ll need to modify your settings later.

> **Note:**
> When you terminate an employee, if the employee is included in any Supergroups, the offboarding flow will notify you so you can make any necessary changes.

* * *

## Who is included when you add All - Everyone

When you create a Supergroup, you can include the predefined category **All - Everyone**.

This group will include active employees and contractors of all employment types. It will NOT include third-party or external admins.

Service accounts are not included in predefined Supergroup categories such as _All-Everyone_. You must explicitly add a service account in a Supergroups box for it to be included in the group. For more information, see [Overview of service accounts](https://developer.rippling.com/documentation/rippling-platform/users/service-accounts).

* * *

## Limitations for complex Supergroups

When creating Supergroups, it’s possible to set up a highly complex set of rules for who to include in the group. Some complex Supergroups may take a minute or two to populate with members. In this case, you’ll see a message noting that it could take a minute to build the group.

It's possible to set up a group that's too complex to populate in a timely manner. If that happens, you’ll see a message letting you know the Supergroup is too complex. You won’t be allowed to save the Supergroup until you simplify it.

* * *

## Evaluation timeframe

By default, Supergroups include people based on their current attributes in Rippling, their current department, title, location, etc. However, there may be occasions when you need to create a Supergroup that includes people based on what their attributes are during a specific period of time.

### Examples

**Employees move to a different location.** It’s November, and you’re getting ready to send out a survey about a parking issue that occurred at the Chicago office in October. You don’t want November new hires and employees who have transferred to a different office to be asked to participate, since the survey isn’t relevant to them. When selecting survey participants, set the evaluation timeframe to include only people who were based in the Chicago office at any point during the month of October.

**Hourly employees transition to salaried.** Your hourly employees track their time in Rippling. When someone moves into a salaried position, they no longer need to access the time tracking app, and their access is revoked automatically based on the Supergroup definition. However, this prevents people from being able to log their hours during their last month as an hourly employee. When defining access to the time tracking app, set the evaluation timeframe to include people who were hourly employees at any point during the last 30 days.

**Sales employees transfer departments or depart the company.** Your sales staff are paid commissions on a quarterly basis. But when sales people leave the department or the company mid-quarter, they are inadvertently excluded from your commission calculations. When defining who is eligible to be paid commissions, set the evaluation timeframe to include anyone who was in the Sales department during the quarter.

### Scope and limitations

To optimize performance, Rippling only stores enough historical data needed to support the most common use cases. Because of this, Supergroups based on point-in-time calculations have the following limitations.

**Supported attributes.** You can only use the following attributes:

-   Status as a manager
-   Status as an admin
-   Department
-   Work location
-   Teams
-   Level
-   Employment type

**Supported time ranges.** Time ranges are limited to the following:

-   The range can start as early as Jan. 1, 2016.
-   The range can extend 3 months into the future.
-   Ranges are defined by date, not by a specific time.
-   All dates are calculated using UTC.

**Uses in Rippling.** Supergroups based on point-in-time calculations cannot be created in the following places:

-   Saved Supergroups app
-   Automation Studio
-   In the sharing component (such as when sharing a report or automation)
-   When sending documents

If you add an evaluation timeframe to a Supergroup that includes attributes that aren’t supported, those attributes will be shaded red. They will be ignored when the Supergroup membership is evaluated. We recommend removing these attributes.

## See also

-   [Get started with the Supergroups API](https://developer.rippling.com/documentation/rest-api/guides/supergroups-getting-started)
-   [Permissions for data in Rippling](https://developer.rippling.com/documentation/rippling-platform/data-model/permissions)
-   [Object permissions](https://developer.rippling.com/documentation/rippling-platform/data-model/object-permissions)
-   [Overview of service accounts](https://developer.rippling.com/documentation/rippling-platform/users/service-accounts)
-   [Automation permissions](https://developer.rippling.com/documentation/rippling-platform/developer/workflows/permissions)

Source: https://developer.rippling.com/documentation/rippling-platform/supergroups/getting-started

> For the complete documentation index, see [llms.txt](https://developer.rippling.com/llms.txt). Public pages have a Markdown version at the same URL with .md added.
