Product · free template

New User Account Request

Request accounts for a new starter: who they are, start date, team and manager, what they need access to, equipment, and manager approval before setup.

A ready-to-use technology, saas & dev form for engineering, IT and product teams: 24 questions, 2 pages, 4 conditional rules.

Questions
24
Pages
2
Layouts
classic
Time to complete
≈ 6 min
Conditional rules
4
Preview it in the gallery

Searches this template answers

Also filed under

Live preview and test console

This is the real form. Answer it to test the flow — nothing is sent or stored.

Page 1 of 2 — The new starter

Who is joining, and when

Is this a fixed-term or contract role?
Where will they mostly work?

This template runs as a straight sequence — no branching rules.

Compliance checklist

Ready to publish
  • Payment items priced — passingEvery payment question charges a real amount, so a submission always records a payment.
  • Conditional logic resolves — passingEvery rule points at a question or page that exists in this template.
  • Legal text not required — passingThis template collects neither health nor regulated financial information.
  • Question labels unique — passingLogic and exports address questions by label, so duplicates are ambiguous.

What happens after submit: nothing is stored in this preview. On your own copy, every response triggers an instant email notification and lands in your response dashboard, ready to export or forward.

Happy with it? Take a copy into your workspace — every question, rule and setting comes with it.

Who this template is for

New User Account Request is built for engineering, IT and product teams who need to route technical requests with the context needed to triage them.

  • Engineering, IT and product teams working in technology, saas & dev.
  • Teams who need to route technical requests with the context needed to triage them without writing code or paying for a custom build.
  • Anyone replacing vague reports that can't be reproduced or prioritised with one structured record per enquiry.
  • Respondents are users, testers and internal stakeholders — the form asks them 24 questions across 2 screens.

Why this form is useful

It removes the cost of vague reports that can't be reproduced or prioritised and turns each submission into a record your team can act on immediately.

  • 18 questions are required, so submissions arrive complete instead of needing a follow-up email.
  • It collects a verified email address so replies and confirmations land.
  • It records a signature you can keep as proof of agreement.
  • It pins the request to a specific date.
  • It allows multiple selections without free text.
  • Conditional logic hides 4 questions until they are relevant — shorter forms convert better than long ones.
  • Splitting the form across 2 pages keeps each screen short and shows respondents how much is left.
  • Every response is stored, searchable and exportable, so nothing depends on one person's inbox.

How to use this template

From copy to live form is a few minutes of work, and every step is reversible.

  1. 1Press “Use this template” — a fresh copy of New User Account Request lands in your workspace, ready to edit.
  2. 2Rename or delete any question, and change what is required. Nothing here is fixed.
  3. 3Open Notifications and add the email addresses that should be alerted on each submission; add an auto-reply to the respondent if the form collects an email address.
  4. 4Publish it, then either share the link directly or paste the embed snippet into your site — the embedded form resizes to fit and loads no marketing or advertising trackers.
  5. 5Watch responses land in Submissions, where you can filter, label and export them to CSV or PDF.

Logic and conditions blueprint

Exactly how this form behaves as it is answered — 4 conditional rules ship with it.

  • Features conditional validation: if “Should their access match someone already here?” is Yes, “Whose access should be used as the starting point” becomes mandatory before the form can be sent.
  • Features conditional validation: if “Will they handle customer or personal data?” is Yes, “What kind of data, and for what tasks” becomes mandatory before the form can be sent.
  • Features conditional validation: if “Is this a fixed-term or contract role?” is Yes, “Date their access should end” becomes mandatory before the form can be sent.
  • Features conditional validation: if “Do they need a company phone number?” is Yes, “Mobile or desk phone” becomes mandatory before the form can be sent.
  • All 4 rules are editable in the Logic tab, and the built-in checker warns about rules that contradict each other.

About this template

New starters lose their first morning when nobody told IT they were coming. This form is written for the manager making the request, not for the person who will build the account, so every label says what the new starter needs to do rather than what a system is called. The first page covers the person: full name, the name they prefer to be called, job title, team, their manager, start date, whether the role is permanent, fixed term or contract, and where they will work. The second page covers what they need: email and calendar, shared drives or folders by name, the tools their team uses, whether they need to approve spending or see payroll information, whether they will handle customer data, and someone whose access is a fair template to copy. It asks whether the new starter needs a phone number, a desk phone or a company card, and finishes with manager approval and the date access should start. Because copying an existing person's access is offered as a starting point rather than a shortcut, IT still reviews what is granted.

What this form asks

Every question is editable — rename it, make it optional, or delete it entirely.

Page 1 — The new starter

  • Full namerequired
  • Name they prefer to be called
  • Job titlerequired
  • Team or departmentrequired
  • Their managerrequired
  • Start daterequired
  • Is this a fixed-term or contract role?required
  • Date their access should end
  • Where will they mostly work?required
  • Personal email for sending setup detailsrequired

Page 2 — What they need

  • Day one essentialsrequired
  • Shared folders or drives they need, by name
  • Tools their team uses that they will needrequired
  • Should their access match someone already here?required
  • Whose access should be used as the starting point
  • Will they approve spending or sign anything off?required
  • Will they handle customer or personal data?required
  • What kind of data, and for what tasks
  • Do they need a company phone number?required
  • Mobile or desk phone
  • Do they need a company card?required
  • Access needed fromrequired
  • Requested byrequired
  • Manager approvalrequired

24 questions in total.

Example of a completed new user account request form

Shows how a manager might request access and equipment for a new starter before their first day.

Full name
Amelia Novak
Job title
Marketing Coordinator
Team or department
Marketing
Start date
2026-04-06
Where will they mostly work?
Office
Should their access match someone already here?
Yes
Whose access should be used as the starting point
Jordan Blake
Requested by
Nora Fitzgerald

Sample data — no real people, addresses or records are shown.

How the form changes as it's filled in

This template ships with 4 conditional rules, grouped into 4 behaviours driven by 4 questions. Everything below is already set up — edit or delete any rule once the template is in your workspace.

Driven by “Should their access match someone already here?”

  • Makes answers required

    If “Should their access match someone already here?” is Yes, “Whose access should be used as the starting point” becomes required before the form can be submitted.

Driven by “Will they handle customer or personal data?”

  • Makes answers required

    If “Will they handle customer or personal data?” is Yes, “What kind of data, and for what tasks” becomes required before the form can be submitted.

Driven by “Is this a fixed-term or contract role?”

  • Makes answers required

    If “Is this a fixed-term or contract role?” is Yes, “Date their access should end” becomes required before the form can be submitted.

Driven by “Do they need a company phone number?”

  • Makes answers required

    If “Do they need a company phone number?” is Yes, “Mobile or desk phone” becomes required before the form can be submitted.

Set it up step by step

  1. 1

    Ask for it with the offer

    Send the link when the start date is confirmed, not the week before, so accounts and equipment are ready on day one.

  2. 2

    Keep the tool list in plain words

    Managers name tools the way their team talks about them; IT translates. Asking for system names produces blank fields.

  3. 3

    Treat 'copy someone' as a draft

    Use the named colleague as a starting point and still review each item, or one person's excess access spreads across a team.

  4. 4

    Carry the end date across

    For fixed-term roles the end date should create the removal task straight away, before anyone forgets.

Mistakes to avoid

  • Requesting accounts two days before the start date, which guarantees a wasted first morning.
  • Copying a leaver's access wholesale, quietly handing a new starter permissions nobody reviewed.
  • Leaving contract end dates blank, so temporary accounts stay live for years.

What it pairs with

Most teams don't run this form on its own. These are the forms and systems it sits next to.

What to do with the responses

Create the accounts, hand over equipment against the hardware request, and diarise the leaver task automatically for any fixed-term end date recorded here.

Works in this layout

Browse classic templates

Forms that overlap this one

These pages cover the same subject ground as the new user account request, matched on the words people actually search for.

Privacy & compliance

This form takes money. Card details are handled by the payment provider and never stored in your response data — you keep the order details, not the card number.

Frequently asked questions

How is this different from a helpdesk ticket?

A helpdesk ticket fixes something for someone who already has an account. This creates the account and the access set for a person who does not exist in your systems yet.

Should managers list system names?

No. Ask what the person needs to do and let IT map it to systems; technical labels are the main reason these forms come back half empty.

Does approval have to be the manager?

The manager approves the request. Anything sensitive — payroll, spending, customer data — should get a second approval in your own routing.

What about equipment?

Laptops, monitors and phones go through the hardware request so stock and delivery are tracked separately from account setup.

Is the New User Account Request template free to use?

Yes. You can preview and test New User Account Request on this page without an account, and take a copy into your own HelloForms workspace on the free plan. There is nothing to install and no card required to publish it.

What does the New User Account Request template ask for?

It asks 24 questions across 2 pages, 18 of which are required. Every question is listed in full further down this page, and each one can be renamed, reordered, made optional or deleted after you copy the template.

Can I edit the New User Account Request form after copying it?

Yes — the copy is entirely yours. Change wording, add or remove questions, switch between the classic layout, restyle it to match your brand, and set who gets notified on each submission.

How does the conditional logic in this technology, saas & dev form work?

4 conditional rules ship with the template: Features conditional validation: if “Should their access match someone already here?” is Yes, “Whose access should be used as the starting point” becomes mandatory before the form can be sent. Features conditional validation: if “Will they handle customer or personal data?” is Yes, “What kind of data, and for what tasks” becomes mandatory before the form can be sent. Features conditional validation: if “Is this a fixed-term or contract role?” is Yes, “Date their access should end” becomes mandatory before the form can be sent. All rules are editable in the Logic tab.

Where do responses to the New User Account Request form go?

Submissions land in your workspace under Submissions, where you can search, filter, label and export them to CSV or PDF. You can also email a notification to your team on every submission and send the respondent an auto-reply.

Can I embed the New User Account Request form on my own website?

Yes. Publish the form and paste the embed snippet into any page or share the direct link. The embedded form resizes to fit its container and loads no advertising or marketing trackers inside the iframe.

Is the signature on this form legally usable?

The template captures a drawn signature and stores it with the submission, along with the timestamp, so you keep evidence of who agreed and when. Whether that is sufficient depends on your jurisdiction and the agreement itself.

Related templates

More forms teams pair with the new user account request.

Related categories

All Technology, SaaS & Dev templates