> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Grant Mailbox Permission in Bulk
> Gives several people full access, send as or send on behalf rights to one mailbox in your client's Exchange Online.
Grant Mailbox Permission in Bulk gives several people the same access to one mailbox in one run: full access to open it, or the right to send as or on behalf of it. Use it when a team needs to work from one mailbox, for example to cover a colleague's leave. [Mailbox Delegation](/core/workflows/mailbox-delegation) works the other way round: it gives one person access to one or more mailboxes. Grant Mailbox Permission in Bulk needs [Microsoft 365 connected](/core/get-started/connect-microsoft-365), with [Exchange access](/core/reference/microsoft-faq#exchange-online) for the client.
## What the form asks
| Field | |
| - | - |
| Mailbox | Required, always on. The mailbox to give access to, picked from the client's users |
| Users to grant | Required by default. Add each person who needs access |
| Access level | Required by default. Full access, Send as or Send on behalf. Everyone you add gets the same level |
| Reason / ticket reference | Optional by default. For your records and the approver; not sent to Microsoft |
There's no auto-map question: full access is always granted with auto-mapping on.
## What it does
1. Creates a ticket in your PSA, if Ticketing is on.
2. Waits for approval, if Approval is Internal or External, or a conditional override matches.
3. Grant Mailbox Access: in the client's Exchange Online, gives each person in turn the access you chose:
* Full access lets them open the mailbox, and auto-mapping adds it to their Outlook.
* Send as lets them send mail that appears to come from the mailbox.
* Send on behalf lets them send mail that shows it was sent on the owner's behalf.
It's one run for everyone. Executions lists it as Core · Bulk Mailbox Permission · the client's name. With Log actions to the ticket on, the ticket also gets a note when the run starts, after Grant Mailbox Access and when the run completes.
Each run grants one access level. To give people full access and Send as, run it once for each. See Microsoft's [Manage permissions for recipients](https://learn.microsoft.com/en-us/exchange/recipients-in-exchange-online/manage-permissions-for-recipients).
## Configure it
Go to **Config**, choose Mailboxes and click Grant Mailbox Permission in Bulk.
| Setting | Where | What it does |
| - | - | - |
| Availability | Header | Internal only, Public form only, Internal + public or Disabled. List on homepage needs a public form. Base config only |
| Mailbox | Form config | Always on: the automation needs it |
| Users to grant, Access level | Form config | Hidden, Optional or Required, and Required by default. Keep them required: a request without users fails at Grant Mailbox Access, and one without a level grants Full access. Can differ per client |
| Reason / ticket reference | Form config | Hidden, Optional or Required. Can differ per client |
| Add field, Add section | Form config | Your own questions. They're saved with the request and can go in ticket templates, but aren't sent to Microsoft. Add client section asks one client only |
| Approval | Execution config | None runs on submit. Internal waits for a teammate or group; External waits for the client's approver, set on each client. Conditional overrides use a different approval when the answers match, for example when Access level is Full access. Let the approver edit the request lets them correct the answers first |
| Ticketing | Execution config | Create a PSA ticket for each run, with its type, priority, status, subject and body. Log actions to the ticket adds an internal or public note as each action completes |
| User directory filters | Execution config | Which users the Mailbox and Users to grant pickers list: licensed, active, no guests, and not in the Entra roles you exclude. Exclude specific users at a client's scope |
Approval, Ticketing and User directory filters are set on Base config and apply to every client unless you override them for one. For how Base config and client overrides work, see [How configuration works](/core/get-started/configure-user-onboarding#settings-for-each-client).
## Troubleshooting
Check User directory filters. Shared mailboxes usually have no licence and leavers' sign-in is blocked, so for that client override the filters and untick **Licensed users only** and **Active users only**.
The client has no Exchange connection in Triggr yet. See [Exchange Online](/core/reference/microsoft-faq#exchange-online).
Open the run in Executions to see the error. People are granted in the order you added them, so anyone before the failure may already have access.
## Related
* [Workflow catalogue](/core/reference/workflow-catalogue)
* [Run a workflow](/core/use/run-a-workflow)
* [Executions](/core/use/executions)
* [Mailbox Delegation](/core/workflows/mailbox-delegation), which gives one person access to one or more mailboxes
* [Shared Mailbox Access](/core/workflows/shared-mailbox-access), which adds or removes one person on a shared mailbox
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.