Grant Mailbox Permission in Bulk in 50 seconds: what it asks, what it does and what you get.
What the form asks
There’s no auto-map question: full access is always granted with auto-mapping on.
What it does
- Creates a ticket in your PSA, if Ticketing is on.
- Waits for approval, if Approval is Internal or External, or a conditional override matches.
- 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.
Configure it
Go to Config, choose Mailboxes and click Grant Mailbox Permission in Bulk.Configure Grant Mailbox Permission in Bulk: every option, step by step (1:29).
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.
Troubleshooting
“Microsoft Exchange integration is not configured for tenant …”
“Microsoft Exchange integration is not configured for tenant …”
The client has no Exchange connection in Triggr yet. See Exchange Online.
The run failed at Grant Mailbox Access
The run failed at Grant Mailbox Access
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
- Run a workflow
- Executions
- Mailbox Delegation, which gives one person access to one or more mailboxes
- Shared Mailbox Access, which adds or removes one person on a shared mailbox

