> 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/org/general/add-devices-of-users-to-group_scheduled.md).

# Add Devices Of Users To Group Scheduled

Add the devices of a user group's members to a device group

{% hint style="info" %}
This is a scheduled runbook. It is designed to run on a recurring schedule rather than being triggered for a single object. See [Scheduling](/automation/runbooks/scheduling.md) for details on how to configure runbook schedules.
{% endhint %}

### Description

Adds the devices of all users in a user group to a device group on every run, so device-based policies can follow user membership. Devices already in the group are skipped, and nothing is removed.

### Location

Organization → General → Add Devices Of Users To Group (Scheduled)

**Full Runbook name**

rjgit-org\_general\_add-devices-of-users-to-group\_scheduled

### Details

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

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Group.ReadWrite.All
    * *Resolves the groups by display name and backs adding devices to the device group*
  * User.Read.All
    * *Lists the user group's transitive user members and reads each user's owned devices*
  * GroupMember.ReadWrite.All
    * *Reads current device-group members and adds missing devices via /groups/{id}/members/$ref*

### Parameters

#### UserGroup

Name or object ID of the group whose members' devices are collected.

| Property            | Value      |
| ------------------- | ---------- |
| Required            | true       |
| Default Value       |            |
| Type                | String     |
| Portal display name | User group |

#### DeviceGroup

Name or object ID of the group the devices are added to.

| Property            | Value        |
| ------------------- | ------------ |
| Required            | true         |
| Default Value       |              |
| Type                | String       |
| Portal display name | Device group |

#### IncludeWindowsDevice

Includes Windows devices.

| Property            | Value                    |
| ------------------- | ------------------------ |
| Required            | false                    |
| Default Value       | False                    |
| Type                | Boolean                  |
| Portal display name | Include Windows devices? |

#### IncludeMacOSDevice

Includes macOS devices.

| Property            | Value                  |
| ------------------- | ---------------------- |
| Required            | false                  |
| Default Value       | False                  |
| Type                | Boolean                |
| Portal display name | Include macOS devices? |

#### IncludeLinuxDevice

Includes Linux devices.

| Property            | Value                  |
| ------------------- | ---------------------- |
| Required            | false                  |
| Default Value       | False                  |
| Type                | Boolean                |
| Portal display name | Include Linux devices? |

#### IncludeAndroidDevice

Includes Android devices.

| Property            | Value                    |
| ------------------- | ------------------------ |
| Required            | false                    |
| Default Value       | False                    |
| Type                | Boolean                  |
| Portal display name | Include Android devices? |

#### IncludeIOSDevice

Includes iOS devices.

| Property            | Value                |
| ------------------- | -------------------- |
| Required            | false                |
| Default Value       | False                |
| Type                | Boolean              |
| Portal display name | Include iOS devices? |

#### IncludeIPadOSDevice

Includes iPadOS devices.

| Property            | Value                   |
| ------------------- | ----------------------- |
| Required            | false                   |
| Default Value       | False                   |
| Type                | Boolean                 |
| Portal display name | Include iPadOS devices? |

[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/org/general/add-devices-of-users-to-group_scheduled.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.