NetID: Service Level
Last modified: January 25, 2012
Standard Service Level
Basic Service Level level
Webapps Only Service Level
Dormant Webapps Service Level
Dormant Service Level
Removed Service Level
Expunged Service Level
Rules for Aging accounts
Standard Service Level
Standard service is automatically available to students enrolled for at least one credit hour in the current semester and for a grace period into the next semester. PHD students enrolled last semester also have Standard service. Users entered in the Gemini (Human Resources Management) system as Student Visitors, Faculty, or Staff are given Standard service level. Other users may have this service level if requested through a CAR form.
With standard service, the user has access to the following resources:
- UTD email inbox on the Zmail email server (Exchange is available on request.)
- General use UNIX server apache
- General use PC labs on campus
- Galaxy, eLearning, and NetID web applications
- Home directory for personal files
- A personal web homepage
- Access to UTD's wireless network
- Access to UTD's VPN web application
Basic Service Level
Basic service level access can be requested by a sponsor through the CAR form instead of the full Standard services.
Students who are not currently enrolled, but can enroll this semester without being readmitted, retain Basic service level. Students who have not enrolled for the last two major semesters (Fall and Spring) must enroll in the next major semester in order to avoid being readmitted.
Admitted students who are qualified to enroll in the next two semesters, can pick up a Basic service level computer account from the NetID web site. (http://netid.utdallas.edu)
Users who are entered in the Gemini (Human Resources Management) system as constituent workers are automatically assigned Basic service level.
With basic service, the user has access to the following resources:
- UTD email inbox on the Zmail email server (Exchange is available on request.)
- Galaxy, eLearning, and the NetID web application
- Access to UTD's wireless network
- If not an incoming student, access to UTD's VPN web application through UNIX login
Webapps Only Service Level
This service level is for users who are applying for admission to UTD but have not been admitted. It can also be assigned to guest accounts. This service level has no information regarding an email inbox or home directory. There is no entry in the AD directory.
With Webapps Only service, the user has access to the following resources:
- NetID and Galaxy web applications
- Access to UTD's wireless network
- If not an applicant, access to UTD's VPN application through UNIX login
Dormant Webapps Service Level
Webapps Only and Dormant Webapps have exactly the same computing privileges. The difference is that a user at Dormant Webapps service level can be reactivated to Basic or Standard service level without losing track of their email inbox or home directory. After 15 days, the email and home directory information is lost if the user is not reactivated.
With Dormant Webapps service, the user has access to the following resources:
- Galaxy and NetID web applications
- Access to UTD's wireless network
- If not an applicant, access to UTD's VPN application through UNIX login
This service level would only be assigned to usertype applicant. It can happen when someone at Standard or Basic service level is aged and the usertype becomes applicant usertype. It can also happen if an applicant sets their password and reactivates an Dormant service level account.
Dormant Service Level
When any user is moved from Standard or Basic service level level to a service level that has no access to UTD computing services, they are first moved to the Dormant service level. At this level, the user's email inbox and home directory remain intact. The user will not be able to receive email. The LDAP and AD records are still in the directory, but blocked or disabled. It is a simple matter to restore full service back to the user. This service level only remains for 15 days.
Removed Service Level
After 15 days at Dormant service level, a user account is aged to the Removed service level. The LDAP and AD records are deleted. Information about the email inbox and home directory is lost.
Users at Webapps Only service level who are aged and whose password has expired will be immediately moved to this service level. Since these users did not have an inbox or email, removal from LDAP and AD is swift.
Expunged Service Level
After approximately two semesters at Removed service level, a user account is aged to the Expunged service level. Some JAMS account information is deleted at this point, keeping the name, utdid, birthdate, netid, and history information.
Rules For Aging Accounts
Each account has an aging date. On this date, the service level is recalculated according to the following rules. If a user fits in multiple categories, the user is given the most generous service level. Note that an account can, and often does, age without any change in service level.
| Category on Aging Date | New Service Level |
| Pseudo User | No change if account is active. |
| Paid Faculty, Staff | Standard |
| Enrolled as a student this semester | Standard |
| Enrolled as a PHD student last semester | Standard |
| Can enroll in the next semester or semester following that | Basic |
| Faculty (sponsorship not renewed) | Basic for 30 days |
| Retiree | Basic |
| Applicant | Dormant Webapps if at Standard or Basic Service Level Webapps Only if at Dormant Webapps and password is current Removed if at Webapps Only and password has expired |
| Other active accounts | Dormant for 15 days |
| Dormant accounts | Removed |
| Removed accounts | Expunged |
Aging also sets a new aging date.
The aging date for students is automatically moved forward when the student is enrolled for the current semester. Admitted students have an aging date set to a mass aging date that allows time to enroll for the next semester.
A batch program runs daily to age accounts that expire that day. The aging dates of February 1, June 15, and September 15 are called mass aging dates, because they are the default aging dates for many automatic account management updates. There are typically thousands of users who will age on that date.
The aging date for students automatically advances as the student enrolls each semester. The aging date for a sponsored account must be periodically reset by the sponsor in order to continue as a sponsored acccount. If a sponsor fails to renew the account and the user is still in the system as a paid staff or faculty member, the user will continue to have a Standard service level courtesy account.
