See also

• http://www.it.cornell.edu/cms/services/netid/leave.cfm
• Services retained by having a sponsored NetID, and services you still lose
• Text of NetID renewal email, from ChemIT (for ChemIT staff's use)
• A sponsored NetID by itself does NOT provide Library access.
• Renewing a "sponsored" NetID
• CCB's sponsored NetIDs
• CCB's NetID procedures
• CCB HR Exit form edit ideas

Please be aware of what happens when you leave the University by going to:

• http://www.it.cornell.edu/services/netid/leave/index.cfm
  • For the first table, imagine a column on the far right called "other" and with no services selected. That's what non-retiring leaving staff and "Former Student (not alumni)" are! (Same as "a person off the street", FWIW.)
• For further details from ChemIT, review:
  • Services retained by having a sponsored NetID, and services you still lose

New process as of 6/30/16

• http://itnews.cornell.edu/new-sponsored-netid-process

Chemistry IT staff have not yet determined how we can best be of service to the department considering the new process.

• Whatever process is used, we must be told of sponsored IDs so the department's inventory of current (and past) Sponsored NetIDs can be kept current.

Old process, FYI

1. Have the responsible faculty member send an email to the department chair (currently David Collum <dbc6>), cc:ing Chemistry IT <ChemIT@cornell.edu>, providing the following information:

• The name of the person who needs a NetID
• The NetID to be extended or reactivated
• Specify how long they need the NetID for, in months. (Maximum of one year of length, and they can be renewed yearly indefinitely as needed)
• The reason the person needs their NetID extended or reactivated

If simply renewing sponsorship (vs. sponsoring the NetID for the first time), no need to request duration or reason. We default to one year unless we are told to do otherwise. Use our email template:

• ChemIT sample NetID renewal email to faculty
• If a NetID is not renewed, Chemistry IT will follow proper exit procedures so we don't forget to close cluster accounts, remove use from AD groups, ensure file shared data is properly curated, etc.
  • Chemistry IT's draft exit procedures.

2. Chemistry IT will provide an authorization form to the departmental chair to sign.

• R:\Chem IT\IT Support\Users & Groups\Account & ID's\SponsoredNetIDChairLetterheadRequestTemplates
  
  • Example: "SponsoredNewFromNormalNetid.docx"

3. Chemistry IT will forward the Chemistry departmental approval to CIT for processing. Processing usually is very quick as a NetID is not being created.

• Scan signed form into a PDF. Send to where?
  • Or instead FAX signed form, but if so, to where?

4. Chemistry IT documents all currently sponsored NetIDs.

• CCB's sponsored NetIDs

5. CIT emails us with a confirmation. And the NetID becomes "sponsored" in Cornell terminology.

We're trying to think of ways to improve this process.