Remember to check the Knowledge Base for a solution before you enter a new ticket.

✕
HelpDesk
sign in

New User Onboarding Request

Creation date: 5/20/2026 1:34 PM    Updated: 7/27/2026 8:47 AM   account-creation hr new-hire new-user onboarding
Print...
Argus IT Help Desk · New Users
New User Onboarding Request — What to Include
The one field that matters most: whose access do we copy from?
✋
Accounts will NOT be created until this form is complete
Incomplete requests are placed on hold and returned for the missing information. Fill in every required field before submitting.
ℹ
To set up a new staff member quickly and avoid back-and-forth, include everything below in your ticket. The single most important item is whose access we should copy from — without it, we can't match the new user's permissions to their role.
📋  The form — copy into your ticket and fill in
NEW USER ONBOARDING REQUEST
===========================

Full legal name:
Preferred name (if different):
Job title:
Reporting to (manager name):
Department:
Property / venue (which hotel or restaurant):
Start date:
Employment type:  [ ] Full-time  [ ] Part-time  [ ] Seasonal  [ ] Contractor

ACCESS REFERENCE - REQUIRED
Whose existing access should we COPY FROM?
   (Name an existing staff member in the same role / department whose
   permissions match what this new user will need.)

Copy access from:

HARDWARE NEEDED
[ ] Laptop (model preference or "standard"):
[ ] Desktop
[ ] Monitor(s) - how many:
[ ] Cell phone (corporate-issued)
[ ] Headset
[ ] Other:

SHIPPING ADDRESS (if hardware is needed and user is not at corporate):
   (Full address including building, room, attention-to)

SYSTEMS / APPLICATIONS THEY WILL USE
[ ] Microsoft 365 (Outlook, Teams, OneDrive) - standard, default yes
[ ] OPERA Cloud (hotel front desk) - which property:
[ ] Squirrel POS (F&B point-of-sale) - which venue and station:
[ ] Optimum Control (F&B inventory)
[ ] Adobe Acrobat - Standard or Pro:
[ ] FortiClient VPN (remote access)
[ ] Other (list):

EMAIL / DISTRIBUTION LISTS
Email aliases the user should also receive at (if any):
Distribution lists to add the user to:
Shared mailboxes the user needs access to:

ADDITIONAL NOTES
(Anything unique - "Will be travelling between properties,"
"Needs admin rights on local workstation," etc.)

APPROVAL
Approved by (manager):
👥  Why "copy access from" matters
Argus IT works off a reference-user model. Tell us "copy access from Jane Doe" and we mirror her shared folders, mapped drives, distribution lists, and most permissions in one go — instead of hours of back-and-forth about every single resource.
💡 Brand-new role with no precedent? Say so — we'll build the access profile manually with the manager.
🚫  Common mistakes
  • "Same access as everyone else" — there's no single "everyone else" set. Always name a specific person.
  • No manager approval — new hires need confirmation from the hiring manager or HR.
  • Last-minute requests — submit at least 3 business days before the start date; hardware and specialty software can take longer.
  • Missing shipping address — the #1 cause of hardware delays.
✅  What happens next
1
Ticket received and triaged — missing info gets a reply asking for it.
2
The account is created (M365 + on-prem AD).
3
Access is mirrored from the reference user.
4
Hardware is ordered or assigned if requested.
5
Credentials go to the manager (NOT the new user) the day before start date.
6
On the start date, the user gets a welcome email with first-login instructions.
🔗  Related
User Off-Boarding Request · How to Request File or Folder Access (KB-30003) · Setting Up Microsoft Authenticator on a New Phone
ArgusIT KB# 30001 · Tags: onboarding · new-user · new-hire · hr · account-creation
Get help for this page Powered by Jitbit HelpDesk