
A free IT service request form template in Excel, Word and PDF: the fields to include, a filled-in sample, service request vs incident, and routing.
A free user account creation request form template: the fields to include, a filled-in sample, who approves new accounts and how to automate provisioning.


Content writer, trio.so
A user account creation request form, also called a new user account request form, is the standard request a manager fills in before IT creates accounts for a new employee, contractor or temporary worker. It records who the new user is and when they start, who is asking, which systems and access levels they need, which device they need, and who approved it, and it leaves a section for IT to note what was created and when. One form per new user gives IT everything it needs in one place, stops access being granted on an email or a hallway request, and leaves a record you can check at the next access review and at offboarding. The fields, a filled-in sample and the free template are below.
If new hires keep arriving with half their access missing, or nobody can say who approved an account, start with the fields table and the download; the rest covers how to run the process.
When accounts are created without a formal request, three problems follow. Access is granted inconsistently, so two people in the same role end up with different rights. Nobody can show who asked for an account or who approved it, which auditors and security reviews will ask for. And IT spends time chasing missing details, such as the start date, the manager or the systems needed, while the new hire waits.
A standard form fixes all three. The requester supplies everything up front, the approval is recorded before anything is created, and IT can set up accounts the same way every time, in line with your access policy and the least privilege access model.
A complete form has these fields. Keep it short enough that managers actually fill it in.
| Section | Fields | Why it matters |
|---|---|---|
| Requester information | Name, role, department, contact details, date of request | Accountability, and someone for IT to ask |
| New user information | Full name, job title, department, manager, employee or contractor, start date, end date if temporary, work location | Decides which role-based access applies and when accounts must be ready |
| Account details | Accounts needed (directory, email, collaboration, business apps), username format, mailbox or licence type | Tells IT exactly what to create |
| Access level and permissions | Each system with the access level (read, edit, admin), shared drives and groups, remote access, any privileged access with a reason | Keeps access to what the job needs; privileged access gets a second look |
| Device | Laptop or desktop, phone, accessories, any special software | Lets IT prepare the device before day one |
| Authorization and approval | Manager approval, system owner approval for privileged or sensitive access, dates | Proves each account was approved before it was created |
| IT department use only | Accounts created, username, groups added, device assigned, created by, date completed, ticket number | The record you check at access reviews and offboarding |
| Field | Example |
|---|---|
| Requester | Dana Reyes, Finance Manager, 3 November 2026 |
| New user | Sam Patel, Accounts Payable Specialist, Finance, employee, start date 17 November 2026 |
| Accounts | Directory and email account, Microsoft 365 licence, chat, accounting system |
| Access | Finance shared drive (edit), accounting system (accounts payable role, no admin), VPN |
| Device | Company laptop, headset |
| Approvals | Dana Reyes (manager), 3 Nov; accounting system owner, 4 Nov |
| IT use only | Accounts created 12 Nov by the help desk, laptop assigned, ticket IT-2481 |
Download the template, then adjust the systems and approvers to match your organization.
Adapt the template to your systems first: list the accounts every employee gets, the ones that depend on the role, and the ones that need extra approval. Make the form easy to find, ideally as a request type in your help desk or service portal so every request becomes a ticket; see the IT service request form template for the wider request process.
A simple approval flow works for most teams: the manager submits the request, the owner of any sensitive or privileged system approves that access, and IT creates the accounts and records what it did. Ask HR to trigger the request as soon as an offer is accepted, so accounts and the device are ready on the first day. Tell managers about the process once, in writing, and reject requests that skip it.
The form starts onboarding; these steps finish it. The IT onboarding checklist covers them in more detail.
Create the accounts listed on the approved form, add the user to the groups for their role, and give only the access that was approved. Turn on multi-factor authentication for every account that supports it. Where your identity provider can provision accounts into other apps automatically, use it, so access follows the role instead of being set by hand; see user provisioning.
Prepare the device before the start date: enroll it in your device management tool, apply encryption and security settings, and install the apps the role needs. A device that arrives ready means the new user can sign in and work on day one.
Walk the new user through the policies that apply to them: acceptable use, passwords and MFA, how to spot and report phishing, and how to handle company data. Record that it was done.
Because every account starts with an approved form, you have a record of who asked, who approved and what was created. That record is what you compare against at each user access review, and it is how you spot excessive permissions that crept in later. Frameworks and auditors usually ask for exactly this evidence: that access was approved before it was granted and reviewed afterwards.
The same record makes offboarding faster. When the person leaves, the IT-use-only section lists every account, group and device to remove or collect; see the IT offboarding checklist.
Once a request is approved and the account exists in your directory, the user does not need to be retyped into your device console. trio.so syncs users from Microsoft Entra ID or Google Workspace, and supports SCIM 2.0 user provisioning with Microsoft Entra ID, so new users appear in trio.so from the directory.

A user account creation request form makes every new account start the same way: requested by a manager, approved before it exists, created to match the role, and recorded. Use the fields above or the free template, route requests through your help desk, and keep the completed forms for access reviews and offboarding.
trio.so syncs users from Microsoft Entra ID or Google Workspace and supports SCIM provisioning with Entra ID.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.





Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.
Related
The related industry news, interviews, technologies, and resources.

A free IT service request form template in Excel, Word and PDF: the fields to include, a filled-in sample, service request vs incident, and routing.

Free data encryption policy template in Word and PDF: at rest and in transit, approved algorithms, key management, a checklist and an Excel key register.

A free penetration testing policy template in Word, PDF and Excel: the sections to include, a test plan example, rules of engagement and reporting.

Free data classification policy template in Word and PDF: four levels with examples, a handling matrix, labeling rules, forms and an Excel register.

Free email and electronic communication policy in Word and PDF: approved apps, phishing, a monitoring notice and an email retention schedule.

Free remote access policy template in Word and PDF: approved methods, RDP and MFA rules, vendor access, logging, an acknowledgment form and an Excel register.

Free social media policy template for employees in Word and PDF: personal and official accounts, account security and a hacked-account checklist.

Free mobile app security policy in Word and PDF: approved app sources, app vetting, blocked apps and permissions, plus an Excel app register.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients