Guidelines for Administrative NetID Creation
Since most Administrative NetIDs are created for email purposes, the items here are expressed in terms of email addresses.
- Requests are reviewed by the UIS Identity and Collaboration team.
- Administrative NetIDs must be appropriate under the Computer Systems Acceptable Use Policy, including limitations on shared passwords.
- Most three initial combinations are unavailable for Admin NetIDs due to previous assignment for individual use.
- Administrative NetIDs may not be too broad or misleading
- Example:teaching@georgetown.edu is too broad to be granted to an individual person or academic department.
- Administrative NetIDs that may be needed by another department or group will not be granted.
- Example: german@georgetown.edu will not be granted to the German Club since the German Department might need it.
- Administrative NetIDs will not be granted for personal use as a vanity email address
- Example: johnsmith@georgetown.edu will not be granted for John Smith?s email.
- Administrative NetIDs may not contain dates.
- Example: jesuitweek2003@georgetown.edu will not be granted.
- Administrative NetIDs will not be created for short-term or one-time events.
- Administrative NetIDs may not contain the name of the owner.
- Example: smithresearch@georgetown.edu will not be granted.
- Administrative NetIDs are limited to 20 characters (before the @georgetown.edu).
- Administrative NetIDs must consist of numbers and letters, not punctuation marks
- Example: sfs-faculty@georgetown.edu cannot be granted.
- Administrative NetIDs may not be slogans or taglines.
- Example: electnader@georgetown.edu will not be granted.
- Administrative NetIDs may not contain trademarked brand names.
- Example: macromedia@georgetown.edu will not be granted.
- Administrative NetIDs are not created for departments to enable generic login.
- Administrative NetIDs are not created in the format of a job title.
- Example: biostatsTA@georgetown.edu.