> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/group/general/add-or-remove-nested-group.md).

# Add Or Remove Nested Group

Add a nested group to this group or remove it

### Description

Adds another group as a member of this group, or removes that nesting again. Works for Microsoft Entra ID groups as well as Exchange Online distribution and mail-enabled security groups.

### Location

Group → General → Add Or Remove Nested Group

**Full Runbook name**

rjgit-group\_general\_add-or-remove-nested-group

### Details

| Property         | Value                               |
| ---------------- | ----------------------------------- |
| Version          | 1.0.3                               |
| Required modules | RealmJoin.RunbookHelper (>= 0.8.10) |
| Schedulable      | no                                  |

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Group.ReadWrite.All
    * *Reads target and nested group and backs the nesting changes*
  * GroupMember.ReadWrite.All
    * *Checks nesting and adds or removes the nested group via /groups/{id}/members/$ref*
* **Type**: Office 365 Exchange Online
  * Exchange.ManageAsApp *(optional — feature: Mail-enabled groups)*
    * *Manages nesting via the Exchange Online distribution group cmdlets*

#### RBAC roles

* Exchange Administrator
  * *Required for the app-only Exchange Online session managing distribution group nesting*

### Parameters

#### GroupID

Object ID of the group the runbook acts on. Set by the portal from the selected group.

| Property         | Value                                  |
| ---------------- | -------------------------------------- |
| Required         | true                                   |
| Default Value    |                                        |
| Type             | String                                 |
| Hidden in portal | yes (preset via runbook customization) |

#### NestedGroupID

Group that becomes a member of this group, or stops being one.

| Property      | Value  |
| ------------- | ------ |
| Required      | true   |
| Default Value |        |
| Type          | String |

#### Remove

Add makes the chosen group a member of this group. Remove takes an existing nesting away.

| Property            | Value   |
| ------------------- | ------- |
| Required            | false   |
| Default Value       | False   |
| Type                | Boolean |
| Portal display name | Action  |

**Portal options**

| Portal option       | Value |
| ------------------- | ----- |
| Add nested group    | false |
| Remove nested group | true  |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/automation/runbooks/runbook-references/group/general/add-or-remove-nested-group.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.