> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/email/reports/calendar-permissions.md).

# Calendar Permissions

This report shows who has been granted access to whose calendar across the selected tenant. It can be read either way round, listing what each user can see or listing who can see each calendar, which makes it a quick way to audit delegated calendars without checking mailboxes one at a time. Unwanted grants can be removed in bulk from the table.

## Action Buttons

<details>

<summary>By User / By Calendar</summary>

Switches how the report is grouped. **By User** is the default and gives one row per user with the calendars they can reach. Clicking it changes to **By Calendar**, which gives one row per calendar with the users who can reach it. The columns and the removal options change with the grouping.

</details>

## Table Details

In the **By User** grouping:

| Column            | Description                                                                          |
| ----------------- | ------------------------------------------------------------------------------------ |
| User              | The person who has been granted access to one or more calendars.                     |
| User Mailbox Type | The kind of mailbox that person has of their own, or `Unknown` where they have none. |
| Permissions       | The calendars this person can reach. See the note below.                             |

In the **By Calendar** grouping:

| Column                | Description                                                        |
| --------------------- | ------------------------------------------------------------------ |
| Calendar UPN          | The address of the mailbox whose calendar the row describes.       |
| Calendar Display Name | The friendly name of that mailbox.                                 |
| Calendar Type         | The kind of mailbox, for example `UserMailbox` or `SharedMailbox`. |
| Permissions           | The users who can reach this calendar. See the note below.         |

**Permissions** is a button labelled with the number of entries behind it. Clicking it opens the detail: in the **By User** grouping that is the calendar, its address, the access rights, and the calendar folder name, and in the **By Calendar** grouping it is the user, the access rights, and the folder name.

The `Default` and `Anonymous` entries that every calendar carries are left out, so a calendar with no explicit delegate does not appear at all. The folder name is worth reading where a mailbox was created in another language, because the calendar folder is named in that language rather than being called Calendar.

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Bulk Remove Calendar Permissions</td><td>Takes away the grants you choose from the selected row(s). The list of grants to remove is built from the rows you selected, so it only ever offers grants that really exist. In the <strong>By User</strong> grouping you pick calendar and access right pairs and the selected users lose access to those calendars; in the <strong>By Calendar</strong> grouping you pick user and access right pairs and those users lose access to the selected calendars. Each grant is removed from the calendar folder it was found on, so calendars named in another language are handled too. Rows from several tenants can be selected together when viewing all tenants.</td><td>true</td></tr></tbody></table>

Both groupings are refreshed once the removal completes, so the report reflects the change straight away. The `Default` and `Anonymous` entries are not listed, so they cannot be removed from here.

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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.cipp.app/user-documentation/email/reports/calendar-permissions.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.