Can this form be eSigned?

Yes. Electronic signatures meeting the ESIGN Act (15 U.S.C. ch. 96) and state UETA/ESRA rules are valid for deactivation approvals. Ensure intent, consent, signer attribution, and reliable record retention are captured.

Is notarization required?

Routine deactivation requests rarely require notarization. If an employer attaches a notarized affidavit or termination agreement, follow state notary rules. For legal certainty, consult counsel for contract-heavy separations.

How quickly should IT act?

Organizations commonly set an IT SLA of 24 hours or less after approval. For security-sensitive roles or terminations for cause, immediate or same-day revocation is recommended.

What if an account is missed?

If access persists, log the incident, isolate affected systems, revoke any active sessions and tokens, and perform a privileged-access review to determine exposure and remediation steps.

Do healthcare deactivations need extra steps?

Yes. For systems handling PHI, ensure the vendor BAA is in place, revoke PHI access promptly, and preserve audit logs for six years as required by 45 CFR §164.530(j).

How long should records be retained?

Retention depends on applicable laws: IRS records three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and many employers retain termination documentation seven years for employment defense.

Electronic Signature
Templates
HR
Employee User Deactivation Request

Employee User Deactivation Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

EMPLOYEE USER DEACTIVATION REQUEST

Request Date: Requestor Department:

Employee Personal Information

Full Legal Name Employee ID Home Address

Primary Phone

Work Email

Position Information

Job Title

Department

Reporting Manager

Start Date

Current Annual Salary

Employment History (Most Recent Two Employers)

Employer 1 — Company Name

Responsibilities Reason for Leaving Employer 2 — Company Name

Responsibilities Reason for Leaving

Education

Highest Degree Institution Graduation Date

Professional References (3)

Reference 1 — Name

Reference 2 — Name

Reference 3 — Name

Deactivation Details

Effective Deactivation Date: Requested By (Name):

Deactivation Type: Permanent deactivation Temporary suspension Access reduction for role change

Systems / Accounts to Deactivate (check all that apply and provide username)

Corporate Email

Active Directory / Domain

VPN / Remote Access

HRIS / Payroll

Finance / ERP

Other Systems / Special Accounts

Mailbox Retention (days): Archive Required: Yes No

Reason for Deactivation (select all that apply)

Termination Resignation Extended Leave Role Change

Provide factual details supporting the reason for deactivation

Assigned Hardware & Data Recovery

Assigned Devices (list serial numbers where available)

Devices Returned: Yes No

Data Handling Instructions

Security, Compliance and Legal Notices

Authorization: By submitting this form the requestor certifies that they are an authorized representative of their department and that the requested deactivation is necessary for operational, security or personnel reasons. IT is authorized to disable access, suspend credentials, recover devices, and preserve relevant logs and data in accordance with company policy and applicable law.

Data Preservation and Legal Hold: If there is a pending legal hold, litigation, or regulatory obligation involving the employee or the department, the requestor must check the applicable box below and provide details. Data subject to legal hold shall not be deleted until release is confirmed by Legal.

Legal hold applies

Authorizations & Certifications

Applicant Certification: I certify that all information provided on this Employee User Deactivation Request is complete and accurate to the best of my knowledge. I authorize the necessary actions by HR and IT to suspend or remove access, retrieve company property, and to take actions necessary to secure company systems. I understand that improper removal of data or failure to preserve records when required by law may result in disciplinary action.

At-Will Employment Statement: Employment remains at-will, meaning either the employee or the employer may terminate employment at any time, with or without cause or prior notice, except as expressly provided in a written agreement signed by an authorized company representative.

Equal Employment Opportunity: The company is an equal opportunity employer. Actions taken in connection with employment status or access revocation are administered without regard to protected characteristics and in accordance with applicable employment laws.

HR / IT Use Only (Do Not Complete if Requestor)

IT Actions Completed (check and initial):
Disabled Email
Disabled Domain Account
Recovered Devices

IT Notes

Authorization — Requestor Signature

By signing below, the requestor confirms authorization to initiate the actions described in this request and acknowledges the certifications and notices above.

Requestor Printed Name:

By:

Date:

What the Employee User Deactivation Request Is

An Employee User Deactivation Request is a formal, auditable record used to remove an employee's access to company systems, applications, and data when employment status changes or access is no longer required. The document identifies the account(s) to be disabled, the effective deactivation date and time, approvals from HR or management, and any required steps for benefits, payroll, or device recovery. It creates a clear chain of responsibility for IT and security teams, supports compliance with privacy and access-control policies, and provides documentation for audits and incident response.

Why a Standardized Deactivation Request Matters

A standardized request reduces operational risk by ensuring consistent removal of access, minimizing unauthorized access windows, and preserving evidence for audits and regulatory compliance such as ESIGN, UETA, HIPAA, and state privacy laws.

Teams That Use the Deactivation Request

Multiple teams rely on a clear deactivation workflow to protect data, close accounts, and document authority before and after an employee departs.

Human Resources — Initiates requests, confirms termination or role change, and documents approvals for benefits and payroll.
IT / Security — Executes account disablement, revokes credentials, removes device access, and updates directory services.
Line Managers — Verify job impact, confirm return of assets, and approve the deactivation scope.

Coordinated use by these groups ensures timely action and reduces exposure to data leakage, payroll errors, and compliance gaps.

Primary Signers and Approvers

HR Manager

HR Manager — Confirms employment status change, records termination or transfer details, and provides official approval to proceed. HR retains the completed request as part of the employee record for compliance and audit purposes.

IT Administrator

IT Administrator — Receives the request and implements account deactivation, credential revocation, and device recovery. The administrator logs actions taken, timestamps, and any exceptions to support audits and incident investigations.

Essential Components of a Proper Deactivation Request

A professional Employee User Deactivation Request contains structured fields that make it actionable for HR, IT, and security teams and that support retention, audit, and legal defensibility.

Requester Details

Name, job title, department, and contact information for the person submitting the deactivation request so follow-up is possible.

Employee Identity

Employee full legal name, employee ID, work email, and primary username to precisely identify accounts to be deactivated.

Accounts & Systems

A clear list of accounts, applications, administrative roles, VPN and cloud access, and device identifiers that must be disabled or recovered.

Effective Date

Exact deactivation date and time (use MM/DD/YYYY and 24-hour or time zone notation) to align with payroll and benefits cutoffs.

Approvals

Signatures or eSign confirmations from manager and HR to authorize the change and document intent and consent under ESIGN/UETA frameworks.

Post-Action Notes

Fields for documenting account closure confirmations, device returns, exceptions, and the administrator who completed the work.

Step-by-Step: Submit and Process a Deactivation Request

Follow these steps to ensure timely, auditable deactivation and to coordinate HR, IT, and managerial responsibilities.

01

Prepare Request: Complete all required fields and attach supporting documentation.
02

Manager Approval: Line manager reviews and signs to confirm role impact and asset return.
03

HR Authorization: HR confirms status change and authorizes processing for payroll and benefits.
04

IT Execution: IT disables accounts, revokes tokens, and documents completion in the request.

Typical Digital Workflow Settings for Automated Deactivation

Configure these settings when creating an online form or workflow to automate routing and execution while preserving auditability.

Field	Configuration
Auto-revoke access	Trigger directory disable on effective date
SSO disable	Remove SSO group membership automatically
Email forwarding	Set automatic forwarding or mailbox hold
Directory sync	Notify IAM system via API or SCIM

Where to Send and How the Request Is Routed

Routing instructions clarify who receives the request and how each recipient should act to complete deactivation.

Submit to HR: HR intake team receives the request and verifies termination details.
Notify Manager: Manager receives an approval task and confirms asset return.
Route to IT: IT receives deprovisioning task with account list and SLA.
Archive Record: Completed request is stored in HR records for retention and audit.

Technical Requirements for Digital Submission and Signing

Ensure the platform you use supports secure eSignatures, audit logs, and integrations with directory and HR systems.

Integrations: Salesforce | Microsoft 365 | NetSuite
File formats: PDF | DOCX | HTML
Authentication: Email link | SMS code | SSO

Use an eSignature provider that supports audit trails, retention, and optional advanced authentication to meet internal and regulatory requirements.

Typical Deadlines and Processing Expectations

Common timelines help set SLAs and align deactivation with payroll, benefits, and legal obligations.

Effective Deactivation Time:

Use the exact requested time to avoid access gaps or premature disabling.

IT Action SLA:

Complete account disablement within 24 hours of approval in most organizations.

Payroll Cutoff:

Coordinate with payroll cycles to avoid incorrect final pay processing.

Benefits Termination:

Notify benefits administrator within plan deadlines to stop coverage correctly.

Record Archiving:

Store the completed request according to retention policy and regulatory requirements.

Key Milestones in the Deactivation Process

A sequential milestone map clarifies responsibilities from request to confirmation and preserves auditability.

01

Request Initiation

Employee status and affected accounts are identified and submitted by HR or manager.

02

Approval Chain

Manager and HR confirm scope and authorize deactivation.

03

Deprovisioning Execution

IT revokes credentials, disables accounts, and recovers devices per scope.

04

Confirmation & Archive

Completion is documented, signed off, and the record archived for retention.

Common Mistakes to Avoid

Omitting exact usernames or account IDs, causing delays while IT locates accounts to disable.
Failing to revoke API keys, tokens, or third-party app grants that persist after account disablement.
Not documenting approvals or using informal chat confirmations, which weakens audit trails and legal defensibility.
Delaying deactivation beyond the effective date, increasing exposure to data access and insider risk.

Risks and Potential Consequences of Improper Deactivation

Unauthorized Access: Data exposure or misuse

Regulatory Fines: Privacy or HIPAA penalties

Payroll Errors: Incorrect final wages calculation

Legal Disputes: Termination or wrongful access claims

Operational Downtime: Service or project disruptions

Reputational Harm: Customer trust erosion

Security and Compliance Data to Record

Encryption: TLS 1.2/1.3, AES-256

Audit Trail: Timestamped action logs

Access Controls: Role-based permissions

Authentication: MFA or SSO

HIPAA BAA: BAA required for PHI

Retention: Secure archived copies

Realistic Scenarios Where a Deactivation Request Is Used

These examples show common circumstances and how the request supports timely, auditable action.

Case Study 1

An employee is terminated for performance

Manager files a deactivation request the same day
IT revokes network and cloud access within three hours, HR archives the signed request to support final payroll reconciliation and future audits.

Case Study 2

A contractor completes an engagement and loses need for access

Project lead submits a scoped deactivation listing only contractor accounts
IT removes cloud roles and API keys while HR confirms contract closure and retains the record for vendor management review.

Comparing eSignature Platforms for Deactivation Requests

Key platform features and starting prices influence which eSignature solution fits your deactivation workflow and compliance needs.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	No free trial	No free trial	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions and Troubleshooting

Answers to common questions about completing, approving, and executing Employee User Deactivation Requests.

Need help? Contact support

Can this form be eSigned?
Yes. Electronic signatures meeting the ESIGN Act (15 U.S.C. ch. 96) and state UETA/ESRA rules are valid for deactivation approvals. Ensure intent, consent, signer attribution, and reliable record retention are captured.
Is notarization required?
Routine deactivation requests rarely require notarization. If an employer attaches a notarized affidavit or termination agreement, follow state notary rules. For legal certainty, consult counsel for contract-heavy separations.
How quickly should IT act?
Organizations commonly set an IT SLA of 24 hours or less after approval. For security-sensitive roles or terminations for cause, immediate or same-day revocation is recommended.
What if an account is missed?
If access persists, log the incident, isolate affected systems, revoke any active sessions and tokens, and perform a privileged-access review to determine exposure and remediation steps.
Do healthcare deactivations need extra steps?
Yes. For systems handling PHI, ensure the vendor BAA is in place, revoke PHI access promptly, and preserve audit logs for six years as required by 45 CFR §164.530(j).
How long should records be retained?
Retention depends on applicable laws: IRS records three years (IRC §6501(a)), HIPAA six years (45 CFR §164.530(j)), and many employers retain termination documentation seven years for employment defense.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now