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

New User Onboarding Request

Creation date: 5/20/2026 1:34 PM    Updated: 5/20/2026 3:00 PM

New User Onboarding Request — What to Include

⚠️ NOTICE: User accounts will NOT be created until this form is completed in full. Incomplete requests will be placed on hold and returned to the submitter for the missing information. To avoid delays, please ensure every required field below is filled in before submitting your ticket.

To set up a new staff member quickly and avoid back-and-forth, please include all of the information below when submitting your ticket. The single most important item is whose access we should copy from — without that, we cannot match the new user's permissions to their role.


Required Information

Copy the block below into your ticket, then fill it 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?
(Provide the name of an existing staff member in the same role / department whose
permissions match what this new user will need. This is how we ensure they get
access to the right shared folders, distribution lists, and systems.)
Copy access from:

HARDWARE NEEDED
[ ] Laptop (specify 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 about this user's role, special access needs, security clearances,
or scheduling — e.g., "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. When you tell us "copy access from Jane Doe," we mirror her shared folder access, mapped drives, distribution list memberships, and most permissions in one go. This saves hours of back-and-forth where we'd otherwise have to ask about every single resource.

If the new user is going into a brand-new role with no precedent, say so — we'll work with the manager to build the access profile manually.


Common Mistakes to Avoid

  • "Same access as everyone else" — there's no single "everyone else" access set. Always name a specific person.
  • Submitting without a manager approval — for new hires, we need confirmation from the hiring manager or HR.
  • Last-minute requests — please submit at least 3 business days before the start date. Hardware orders or specialty software access can take longer.
  • Skipping the shipping address — if hardware needs to ship to a property, missing addresses are the #1 cause of delays.

What Happens Next

  1. Your ticket is received and triaged. If any required info is missing, we'll 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. Login credentials are sent to the manager (NOT to the new user directly) the day before start date.
  6. On the start date, the user receives a welcome email with first-login instructions.

Related Articles

  • User Departure / Deactivation Request — What to Include
  • How to Request File or Folder Access
  • Setting up Microsoft Authenticator on a New Phone

KB-30001 | Created: May 20, 2026