Rutgers Guest Role / NetID Policy
Rutgers University may grant Guest Roles and NetIDs to individuals who require access to University resources but are not directly affiliated with Rutgers as faculty, staff, or students.
Guest Roles/NetIDs provide limited access to selected University applications and services. The specific level and scope of access are determined by the individual application or service owners.
Eligibility and Sponsorship
To obtain a Guest Role/NetID, an individual must be sponsored by an active Rutgers faculty or staff member. The Sponsor must have a legitimate academic, administrative, or business reason for requesting access on behalf of the guest.
Guest Role / NetID Holder Responsibilities
Individuals issued a Guest Role/NetID are required to:
- Comply with all Rutgers University policies, standards, and guidelines, specifically #70.1.7 Rutgers Provisioning/Deprovisioning Policy.
- Adhere to all applicable local, state, and federal laws and regulations.
Violation of University policies or applicable laws may result in immediate termination of the Guest Role/NetID and loss of access to Rutgers systems.
Revocation of Guest Roles / NetIDs
Rutgers University reserves the right to revoke a Guest Role/NetID at any time. If a Guest Role/NetID is revoked, all associated access will be disabled immediately, without prior notice.
Guest Role / NetID Lifecycle and Duration
By default, Guest Roles/NetIDs are granted for a maximum period of 18 months.
- Sponsors may request shorter access periods based on business need.
- Access periods cannot exceed 18 months.
- Sponsors are strongly encouraged to set the shortest duration necessary.
- Guest Roles/NetIDs may be renewed if continued access is required.
Expiration Notifications
Sponsors and guests will receive email notifications 30 days prior to the expiration date to confirm whether renewal is required. If no action is taken by the sponsor, the Guest Role/NetID will be automatically disabled on the expiration date.
Segregation of Duties
A Sponsor must not act as the Guest Admin for the same Guest request. This separation of duties helps prevent conflicts of interest, reduces the risk of unauthorized access, and ensures proper oversight throughout the Guest onboarding process.
