n8n mailbox permission request form
Build a mailbox permission request form for n8n with tenant-specific users, mailbox choices, access level, approval, and Microsoft 365 handoff.
An n8n mailbox permission request form should collect the customer, target mailbox, user receiving access, permission type, duration, justification, and approval before n8n changes mailbox permissions.
Mailbox permissions are easy to request badly and hard to audit later. The form should turn the request into a structured approval and fulfillment contract.
Require approval from the mailbox owner, manager, or customer contact before granting access to a mailbox.
Build the form contract before the n8n fulfillment branch.
Load mailbox options
Use an n8n webhook to return tenant-specific mailbox choices with stable IDs.
Capture recipient and permission
Use controlled fields for the user receiving access and the permission type.
Ask for justification
Collect why access is needed and whether it should expire.
Route approval
Send approval to the mailbox owner, manager, or customer contact.
Fulfill through n8n
Apply the approved permission through Microsoft 365, CIPP, Graph, or PowerShell and update the PSA ticket.
Send n8n the mailbox ID, access recipient ID, permission type, duration, approval result, tenant mapping, and ticket reference.
Can n8n grant mailbox permissions from a form?
Yes, after the request is validated and approved. FormNode collects the structured request; n8n performs the Microsoft 365 permission change.
What mailbox permission fields should the form include?
Include target mailbox, access recipient, permission type, duration, justification, approver, and tenant context.