> 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/security/list-pim-rolegroups-without-owners_scheduled.md).

# List Pim Rolegroups Without Owners Scheduled

Alert on PIM role groups that have no owner

{% 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

Finds role-assignable groups that hold eligible PIM role assignments but have no owner, so nobody is responsible for their membership. The group names are listed and can be sent by email. Nothing is changed.

### Location

Organization → Security → List Pim Rolegroups Without Owners (Scheduled)

**Full Runbook name**

rjgit-org\_security\_list-pim-rolegroups-without-owners\_scheduled

### Details

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

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * Group.Read.All
    * *Lists role-assignable groups and reads their owners to find ownerless ones*
  * RoleManagement.Read.Directory
    * *Queries roleEligibilitySchedules per group to detect PIM-eligible role assignments*
  * Mail.Send *(optional — feature: Email report)*
    * *Sends the alert email via /users/{From}/sendMail when ownerless PIM groups were found*
  * Organization.Read.All *(optional — feature: Email report)*
    * *Reads the tenant's verified domain for the alert email body*

### Parameters

#### SendEmailIfFound

Sends an email with the group names when such groups are found.

| Property            | Value                                |
| ------------------- | ------------------------------------ |
| Required            | false                                |
| Default Value       | True                                 |
| Type                | Boolean                              |
| Portal display name | Send an email when groups are found? |

#### From

User in the tenant the alert is sent as; needs a mailbox.

| Property            | Value                 |
| ------------------- | --------------------- |
| Required            | false                 |
| Default Value       | <reports@contoso.com> |
| Type                | String                |
| Portal display name | Alert sender          |

#### To

Gets the email with the group names.

| Property            | Value                         |
| ------------------- | ----------------------------- |
| Required            | false                         |
| Default Value       | <support@glueckkanja-gab.com> |
| Type                | String                        |
| Portal display name | Alert recipient               |

[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/security/list-pim-rolegroups-without-owners_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.