user offboarding

User offboarding form for IT and MSP workflows

Build a user offboarding form that captures identity, timing, mailbox handling, license removal, delegation, approval, and audit-ready workflow handoff.

Direct answer

A user offboarding form should collect the target user, customer or department context, termination date and time, mailbox action, forwarding or delegation choices, license handling, file access decisions, approval state, and ticket context before automation disables or changes the account.

Offboarding touches identity, email, files, licenses, and customer communication. A workflow form reduces missed steps by making each protected decision explicit before fulfillment.

Field structure

Customer or department	Identifies which tenant, policy, and workflow branch applies.
Target user	Uses dynamic data so the requester chooses the right account.
Termination timing	Controls when access should be blocked or scheduled.
Mailbox handling	Captures convert-to-shared, forward, delegate, or retain decisions.
License and group handling	Controls cost cleanup and access removal.
Approval	Documents signoff before high-risk identity and data changes.

Dynamic data

tenant userslicense assignmentsmailbox listmanager listapproval contactsPSA ticket mapping

Approval boundary

Require approval before blocking sign-in, converting mailboxes, deleting or delegating data, removing paid licenses, or granting access to another user.

Implementation order

Build the form contract before the n8n fulfillment branch.

Scope the request

Attach the customer, tenant, or department context before any account list loads.

Load the target user

Use a dynamic dropdown backed by the identity source instead of free-text account entry.

Capture protected decisions

Ask explicitly about mailbox conversion, forwarding, OneDrive or file delegation, and license removal.

Route approval

Send the request to the manager, customer contact, or internal owner before fulfillment.

Fulfill and record

Send the approved payload to the automation engine and update the ticket or audit record.

n8n handoff

Send the workflow the target user ID, scheduled time, mailbox action, license handling, delegation choices, approval result, tenant mapping, ticket ID, and idempotency key.

Common questions

What should a user offboarding form include?

Include target user, termination timing, mailbox action, forwarding or delegation, license handling, file access decisions, approval state, tenant context, and ticket context.

Should offboarding be fully automated?

Only after the request has the right approval and customer policy context. High-risk identity and data changes should not run from unverified free-text requests.

Can FormNode hand off offboarding to n8n or Power Automate?

Yes. FormNode collects the structured request and approval state, then sends the payload to n8n, Power Automate, Make, Zapier, or a custom API.

n8n user offboarding form IT request form builder Best IT request form builders Webhook form security checklist Microsoft 365 integration