Establishing secure connection…Loading editor…Preparing document…

User Creation Form

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

USER CREATION AGREEMENT AND ACCOUNT PROVISIONING FORM

Parties and Recitals

This User Creation Agreement and Account Provisioning Form (the Agreement) is entered into by and between Requesting Organization: and IT Provider: .

WHEREAS, the Requesting Organization requires creation and provisioning of electronic user accounts and associated access to systems, data, and services;

WHEREAS, the IT Provider is responsible for secure account creation, access configuration, and initial account administration in accordance with the Requesting Organization's policies and applicable law;

WHEREAS, the parties wish to document the scope, terms, and responsibilities governing the provisioning and use of the created user account.

User Account Details

Scope of Work

The IT Provider will create, configure, and deliver the user account and related access as specified below. The scope includes initial credential issuance, assignment of permitted systems, application entitlements, and documentation of assigned privileges.

Access and Permissions

Check all entitlements to be provisioned for this account:

Account Settings & Security

Password expiry (MM/DD/YYYY):

Account expiration (if applicable) (MM/DD/YYYY):

Approval & Acknowledgment

Approval date (MM/DD/YYYY):

Payment Terms (If Applicable)

If account provisioning or recurring user-management services are billable, the following payment terms apply.

Late payment fee: . Fees are cumulative and calculated on unpaid outstanding balances.

Term and Termination

This Agreement commences on Start Date: and continues until End Date: unless earlier terminated in accordance with this section.

Either party may terminate for convenience upon written notice of days. Immediate termination may occur for material breach, gross negligence, or violation of applicable law or security policy. Termination does not relieve the Requesting Organization of payment obligations incurred prior to termination.

Confidentiality

The parties acknowledge that the account provisioning process may involve access to confidential or personal data. Each party agrees to maintain confidentiality of any proprietary information or personal data accessed under this Agreement and to use such information solely for purposes of account provisioning and administration. The IT Provider will implement and maintain reasonable technical and organizational measures to protect confidentiality and prevent unauthorized access, disclosure, alteration, or destruction of data.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the state of: , excluding its choice-of-law rules. The parties submit to the exclusive jurisdiction of courts located within that state for disputes arising under this Agreement.

Representations; Entire Agreement

Each party represents that it has the authority to enter into this Agreement and to perform its obligations hereunder. The Requesting Organization certifies that it has the right to request the provisioning of the specified access for the named user and that such access is appropriate for the user’s duties.

This Agreement constitutes the entire agreement between the parties with respect to the subject matter herein and supersedes all prior understandings, proposals, and communications, whether written or oral. Any amendment must be in writing and signed by authorized representatives of both parties.

Audit, Records and Compliance

The IT Provider will maintain records of account creation, entitlement assignments, and approvals for a minimum of . Upon reasonable request, the IT Provider will permit the Requesting Organization to audit provisioning records to confirm compliance with this Agreement, subject to legitimate confidentiality protections.

Acknowledgment of Acceptable Use

The user shall be informed of applicable acceptable use, privacy, and security policies prior to activation. The Requesting Organization acknowledges responsibility for ensuring the user completes required training and accepts these policies prior to receiving access.

Requesting Party:

By:

Date:

IT Provider:

By:

Date:

Enter text✕
Prepare your document for signing right on this page
  • 01 Edit the text and complete the fields
  • 02 Click Sign Now and on the next screen add recipients and signature fields in SignNow
  • 03 Start your free trial to sign and send your doc
Sign Now

What the User Creation Form Is and when it’s used

A User Creation Form is a standardized record used to request and authorize new user accounts, system access, and associated privileges within an organization. It documents the requester, approver, required systems, role or access level, start date, and any supporting approvals or legal acknowledgments. Organizations use the form to ensure consistent provisioning, enforce least-privilege access, and create an audit trail for compliance reviews. The form can be paper, fillable PDF, or an online workflow and is often tied to identity providers and access-management systems.

Why a clear User Creation Form matters

A well-designed User Creation Form reduces onboarding errors, enforces access policy, and provides an auditable record for security and compliance reviews. It improves handoffs between HR, IT, and managers while minimizing privilege creep and operational delays.

Why a clear User Creation Form matters

Who typically completes and approves this form

The User Creation Form is completed by requestors and processed by IT or identity teams, with managerial and HR approvals where required.

  • Hiring managers — submit role, start date, and required systems; verify business need for access.
  • IT / Identity administrators — review the request, map roles to permissions, and provision accounts.
  • HR and security teams — confirm employment status and ensure onboarding checks are complete.

Use role-based routing to send the form automatically to required approvers and to capture an audit trail of each decision.

Step-by-step process to request and provision a user account

Follow these sequential steps to ensure requests are approved and accounts are provisioned consistently.

  • 01
    Submit Request: Requester completes the form and attaches approvals or role justification.
  • 02
    Manager Approval: Manager confirms business need and required access levels.
  • 03
    IT Provisioning: Identity team creates account, assigns role, and configures MFA.
  • 04
    Notification: Provisioned user receives credentials, onboarding steps, and security guidance.

Typical online workflow settings for automated provisioning

Configure digital workflows to capture data, route approvals, and call provisioning APIs automatically.

Field Configuration
Identity Provider Connect to SAML/SCIM-enabled IdP for automatic user sync
Provisioning Mode Automated provisioning with manual approval step
Authentication Enforce MFA and conditional access policies
Role Mapping Map form role to directory groups and permissions

Where to send the completed form and how routing works

Route the completed form through an approvals workflow so IT receives validated requests ready for provisioning.

  • Ticketing System: Submit the form to ITSM or helpdesk for tracking and SLA measurement.
  • Automated API Call: Approved requests trigger directory provisioning via SCIM or API integration.
  • Approval Audit: Workflow records manager and HR approvals for audit trails.
  • User Notification: System sends account details and next steps automatically to the new user.

Sharing, signing, and system integration considerations

Choose platforms that support secure forms, eSignature, and integration with your identity and ITSM tools.

  • Supported Integrations: Salesforce, NetSuite, Google Workspace
  • Document Formats: PDF, DOCX, HTML supported
  • Authentication Options: Email, SMS, KBA, SSO

Integrations reduce manual steps: connect forms to IdP, HRIS, and provisioning APIs to accelerate secure onboarding.

Typical eSignature vendor comparison for signing onboarding forms

Compare basic pricing and common features for digital signature providers; signNow is listed first per platform data.

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 No 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

Essential fields to capture on the form

Username: Unique account name
Email: Corporate email address
Employee ID: HR or payroll identifier
Role: Standardized role code
Systems: List of target systems
Start Date: MM/DD/YYYY format

Common mistakes to avoid when preparing the form

  • Submitting incomplete system lists leads to delayed access and ad hoc follow-up provisioning actions by IT.
  • Using informal role descriptions instead of standardized role codes causes incorrect permission assignments.
  • Failing to attach manager approval or HR confirmation results in rejected requests and audit exceptions.
  • Providing personal email addresses or inaccurate names complicates identity verification and directory synchronization.

Immediate risks and compliance consequences

Unauthorized Access: Security breach risk
Privilege Creep: Excessive permissions accrual
Audit Failure: Noncompliance citation
Payroll Errors: Incorrect pay or benefits
HIPAA Exposure: Protected data risk
Recordkeeping Gaps: Retention violations

How organizations use a structured User Creation Form

Real-world examples show how standard forms reduce provisioning time and improve compliance across systems.

Optica Ventures — onboarding simplicity

When launching new hires we standardized requests and integrated approvals

  • Faster provisioning reduced follow-ups
  • "The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers."

Xerox — NetSuite integration

NetSuite operations linked form data to provisioning APIs

  • Saved manual entry and errors
  • "airSlate SignNow provides us with the flexibility needed to get the right signatures on the right documents, in the right formats, based on our integration with NetSuite."

Core elements to include in a professional User Creation Form

Design the form to collect identity data, approvals, access scope, and compliance acknowledgments so provisioning is auditable and repeatable.

Identity Data

Full legal name, corporate email, employee ID, and contact information to establish identity and match HR records.

Access Scope

Specific systems, applications, and permission levels listed clearly to avoid overbroad access assignment.

Role Approval

Manager and HR sign-offs documented to demonstrate business need and authorization for access.

Security Controls

MFA enrollment, required training, and data handling acknowledgments tied to each provisioning request.

Provisioning Details

Provisioning owner, SLA expectations, and account naming conventions to ensure consistent deployment.

Audit Record

Timestamps, approver identities, and change history to support compliance audits and incident investigations.

Exporting and saving the completed form

Save completed forms in standard formats and retain an immutable audit file for compliance and future reference.

PDF Archive

Export a signed PDF with embedded audit trail for long-term storage and regulatory review; PDF/A preferred for archival.

Structured Data

Export form fields as CSV or JSON for directory provisioning systems and reporting dashboards to automate reconciliation.

Version History

Keep form revisions and approval history accessible to demonstrate chain of custody and changes over time.

Secure Storage

Store signed forms in encrypted cloud or on-prem repositories with access controls and retention policies.

Practical tips for accurate and efficient completion

Follow operational and security best practices to reduce errors, accelerate provisioning, and maintain compliance.

Use standardized role catalogs and naming conventions
Maintain a centrally managed role catalog and ensure requesters pick predefined roles. This reduces manual permission mapping and minimizes over-provisioning.
Require manager and HR approval before provisioning
Automate approval routing so IT only acts on authorized requests. Retain approvals in the audit trail for audits and investigations.
Integrate with identity providers for SCIM provisioning
Where possible, use SCIM or API-driven provisioning to remove manual steps, ensure directory consistency, and enable timely deprovisioning.
Enforce MFA and training prior to granting privileged access
Delay elevated or privileged assignments until users complete MFA setup and any required security awareness training to reduce risk.

Typical timelines and SLAs for processing requests

Define service-level expectations for each stage to set clear deadlines and measure performance.

Request Submission SLA:

Immediate — submit upon hiring approval

Manager Approval:

1–2 business days typical

Provisioning Target:

24–48 hours after approval depending on licensing

Notification Delivery:

Same day as provisioning, where automated

Escalation Timeline:

48 hours without provisioning triggers escalation

How the User Creation Form differs from similar onboarding documents

Compare common onboarding templates to determine which form fits a given operational need.

Form Type | Purpose Form Type Purpose
User Creation Form create accounts and assign initial access
Access Change Form modify existing permissions or roles
Termination / Deprovisioning Form revoke access and schedule offboarding
Privileged Access Request temporary elevated permissions with stricter approvals

Frequently asked questions about the User Creation Form

Answers to common questions about e-signatures, approvals, and provisioning for user account requests.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users
Sign Now
Company
Forms
Pricing
Resources
Knowledge base
Other Products
© 2026 airSlate Inc. All rights reserved.