Understand Account Lifecycles: Difference between revisions

From howdoi
 
(36 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{abox
{{AboxNew
| name         = New User Accounts
| name = Understand Tech Onboarding
| summary      = Hiring a new employee? Go to the section of this document that corresponds with his/her start date. Wondering about a new/visiting/exchange student? Those details are here as well.
| learning =  
| for_employees = Y
| instruction =  
| for_students  =  
| community = x
| for_parents  =
| summ = Learn about the steps we take to create accounts for new employees
| cat1          =  RCS Software and Services
| maintained = RS
| cat2          =
| year = 2024-2025
| maintained   = RS
| year         = 2018-2019
}}
}}
__TOC__


=== Overall Process for New Hires ===
==Overall Process for New Hires==
# New employee submits a signed contract to the Finance Office
# HR creates Veracross record for new employee
# Registrar reviews the record and enters information into Veracross (Ex:schedule)
# Technology department is automatically notified of the new Employee record when the script runs overnight
# Technology department creates accounts for new employee (excluding phone extensions)
# Technology department will send account information to the new hire and/or primary department chair/supervisor


=== New Faculty Members Automatically Get the Following ===
#New employee submits a signed contract to Human Resources (HR)
* Active Directory account (WiFi, Okta, printing)
#HR creates a Veracross record for new employee [Day 1]
* Google Account (GMail, Calendars, Drive, Groups, etc.)
#*Technology/Registrar are automatically notified of the new Employee record overnight
* Schoology account: learning.riverdale.edu
#Registrar reviews the record and enters information into Veracross (Ex: schedule) [Day 2]
#Technology creates accounts for new employee [Day 3]
#Technology will send account information to the new hire
#*The email new users receive directs them to our Getting Started Guide, and asks them to fill out a computer-request form and contact their supervisor from their new account.
 
==New Faculty Members Automatically Receive the Following==
 
* Active Directory account (Okta, WiFi, printing)
* Google Account (Email, Calendars, Drive, Groups, etc.)
* Schoology account = learning.riverdale.edu
* A listing in our Emergency Notification System
* A listing in our Emergency Notification System
* VoiceMail-only phone extension with VoiceMail-to-Email enabled
=== New Employees that are Hired During the School Year ===
# Open a ticket @ https://support.riverdale.edu
# Select '''Tech Support (Exact)'''
# Select '''Need Something New?'''
# Select '''New account creation request'''


=== New Students for Upcoming Academic Year ===
==New Employees that are Hired During the School Year==
* Students enrolled for the coming school year will have accounts created automatically.
The supervisor can ensure an RCS account is created by creating a support ticket:
* This is typically done in the middle of August
# Log into ''support.riverdale.edu''
# Create a new ticket
# Select '''Provisioning'''
# Select '''Employee User Account'''


=== Lifecycle of Accounts for Departed People ===
==New Students for Upcoming Academic Year==
This spreadsheet outlines the various timelines for folks that have departed RCS...


https://docs.google.com/spreadsheets/d/1jedAYBqG0jCw1vh1GEnHM6pcbdMDrNLiTQwEhLuoZ1Q/edit#gid=0
*Students enrolled for the coming school year will have accounts created automatically
*This is typically done in the middle of August


{{SS}}
== When an Employee Leaves Riverdale ==
We ask the supervisor to fill out a ticket for '''EACH''' departing employee so we can process appropriately:
# Log into ''support.riverdale.edu''
# Create a new ticket
# Select '''Provisioning'''
# Select '''Employee User Account'''
# Select '''Deactivate employee user account'''
# Please fill out the questionnaire (one per employee). This creates the ticket so we can process the departing employee's account properly.

Latest revision as of 08:43, 16 September 2024

Howdoi Banner.png
People Graphic.png
Learning Instruction Community
Check Mark Graphic - Unchecked.png Check Mark Graphic - Unchecked.png Check Mark Graphic.png
SummaryLearn about the steps we take to create accounts for new employees
AuthorMaintained by Rob Shin
HelpGet help with this article
StatusUp-to-date for the 2024-2025 school year.

Overall Process for New Hires

  1. New employee submits a signed contract to Human Resources (HR)
  2. HR creates a Veracross record for new employee [Day 1]
    • Technology/Registrar are automatically notified of the new Employee record overnight
  3. Registrar reviews the record and enters information into Veracross (Ex: schedule) [Day 2]
  4. Technology creates accounts for new employee [Day 3]
  5. Technology will send account information to the new hire
    • The email new users receive directs them to our Getting Started Guide, and asks them to fill out a computer-request form and contact their supervisor from their new account.

New Faculty Members Automatically Receive the Following

  • Active Directory account (Okta, WiFi, printing)
  • Google Account (Email, Calendars, Drive, Groups, etc.)
  • Schoology account = learning.riverdale.edu
  • A listing in our Emergency Notification System

New Employees that are Hired During the School Year

The supervisor can ensure an RCS account is created by creating a support ticket:

  1. Log into support.riverdale.edu
  2. Create a new ticket
  3. Select Provisioning
  4. Select Employee User Account

New Students for Upcoming Academic Year

  • Students enrolled for the coming school year will have accounts created automatically
  • This is typically done in the middle of August

When an Employee Leaves Riverdale

We ask the supervisor to fill out a ticket for EACH departing employee so we can process appropriately:

  1. Log into support.riverdale.edu
  2. Create a new ticket
  3. Select Provisioning
  4. Select Employee User Account
  5. Select Deactivate employee user account
  6. Please fill out the questionnaire (one per employee). This creates the ticket so we can process the departing employee's account properly.