Account Requests​

Please carefully review the options below for requesting a guest account. UWSP's guest wireless network is also available for use on personal devices if access to a UWSP network computer is not needed.

Request a Community Visitor Account

Members of the community and UWSP alumni may request a UWSP logon and password that will allow them to log on to designated computers located on the main floor of Albertson Hall for up to 1 hour a day. These computers provide access to the Internet and library catalogs.

To request this type of account visit the Service Desk with a current photo ID.

Community Visitors may pay to print from the Library Circulation Desk or Printing and Design (Lower level of the Science building, room D018). Some local businesses provide duplicating and printing services, which can be found in the yellow pages of the Stevens Point telephone directory.

Please note: Guest accounts are not granted to minors. All UWSP guests accessing the UWSP network have to agree to abide by the UW-System Acceptable Use Policy. Violators of this policy will be denied continued access to the UWSP network and other computer resources.

Student Staff Account Request

Student Staff account is required for any student who may access sensitive data in the course of their work. Student roles that may have access to sensitive data include student employees, research assists, or students working in organizations.

There are two parts to submitting a Student Staff Account request:

  1. You must first complete the request in DIMS to begin the provisioning process, then,
  2. Complete the form here to obtain the necessary Information Security Office approvals.

Student Staff accounts must set up Microsoft multi-factor authentication (MFA) to access secure systems and services.

Due to UW System Administrative Policies 1031 and 1031.A, to comply with data security access and compliance as well as requirements to complete Mandatory Employment Training courses, Information Technology and Human Resources created the below information to support student employment success.

 To Have or Not to Have a Student Staff Account?

Student employees may need a student staff account depending on their relationship with the institution and the level of data they will be accessing. This expectation aligns with UW System Administrative Policies 1031 and 1031.A

Prior to requesting a student staff account, ensure that you review DIMS to determine if a staff account for the student already exists.  Student employees only need one student staff account regardless of number of jobs at UW-Stevens Point. 

To determine if a student employee reporting to you will need a student staff account, use the following scenarios.

Scenarios for student staff accessing moderate to high-risk data:

  1. The student employee attends UWSP as a student: 

    1. If the student employee will not access moderate to high-risk data (See 1031.A) via programs, software, shared network drives, Teams, SharePoint, etc. then the student employee does not need a student staff account. In this situation they can use their normal student account for work related items such as completing timesheets, accessing paystubs, taking mandatory employment trainings, and accessing low risk data (See 1031.A) related to their employment. 

    2. If the student employee will access moderate to high-risk data (See 1031.A) via programs, software, shared network drives, Teams, SharePoint, etc. then the student employee must have a student staff account separate from their student account. 

  2. The student employee does not attend UWSP as a student  

    1. The student employee must have a student staff account. (For example, they may be a student at another educational institution, such as SPASH, Mid-State, etc).

IMPORTANT: Students accessing High-Risk Data

If your student employee's work gives them access to high-risk data as defined in 1031.A (data such as SSNs, personal health information, etc), at minimum they are required to have student staff accounts.

To increase the security layer surrounding high-risk data within your department it is encouraged and preferred that your unit/department requests a role-specific department account be created for your Student Staff to utilize.

A Role-Specific Department Account:

  • Confines high-risk data access to a department-owned account ensuring the data is not made available to individual student staff accounts.

  • Can be restricted in logon access to department computers only.

For more information on how a role-specific account can increase data security within your department, including strategies for limiting logon access of a role-specific account to only your department computer(s), contact the Information Technology Office.

Other Account Request Forms

Please submit Account requests at least three business days in advance.

Administrator Privileges

The ISO is currently researching a system to allow users to request admin rights on a temporary self-service basis. In the meantime, if you require administrative rights over an endpoint, please contact the Information Security Office to make a request directly. Requests for admin access should provide a demonstrable business need for the elevation. This is not the appropriate process for requesting to install software, as every piece of software must be vetted by IT Purchasing and the Information Security Office.

This form is used to begin the approval process for an account that can be given to a presenter or presenters for a workshop, conference, or presentation. It may be used for students taking such a course as well. In both cases, requesting individual account for each presenter/instructor or attendee is preferred, but an account can be shared with approval and adherence to compensating controls, which will be presented upon review of this request. Please fill out the required fields. Once done, the request will be sent to the Information Security Office for review.  

Generic Account Request

Use this form to request an account that will be utilized by a group of individuals, or by individuals filling a specific role. For example, a vendor for the university who provides a service or support for their product and plans to issue the account to a group of service support individuals. Issuing these accounts requires compliance with approved compensating controls and are only allowable in cases where there is a demonstrable technical need. 

Third-Party Account Request

Use this form to request an account for individuals who do not have an appointment with the university, but require access to an IT asset due to a contract, affiliation, volunteer agreement, or other institutional or federative arrangement. This include contractors, visiting lecturers, students from other institutions, UW System employees, and volunteers. 

This form should also be used to request event attendee accounts for conferences, workshops and other events.

Note: The form linked here is only the second part of the process for these accounts. You must first complete the request in DIMS to begin the provisioning process, then complete the form here to obtain the necessary approvals. DIMS can be found here.

Expansion of Entitlements Request

If you already have a UWSP domain account and wish to request access to additional systems, complete the linked form to initiate the request.  For example, if you need to be added to a SharePoint group, or require access to additional modules in AccessPoint. The request process will send notification to the system administrators and approvers responsible for those systems.  You will receive notification when the approval is complete.

Service Account Request

Use this form to request a service account. Service accounts are accounts provisioned in support of a business process or computer system, and are very narrow in terms of scope, usage, and permissions. They are not to be used as logons or "generic admin" accounts. 

Criteria for service accounts:
1) Never used for interactive logon
2) Created and used in support of a technical or business process requiring automation
3) A demonstrable technical need for the account
4) Password must be kept in an encrypted vault
5) 16 character password that meets minimum complexity requirements

Criteria for two-year cycle:
1) All above, plus…
2) Never used for remote logon
3) Password vault only accessible to IT technical contacts supporting the service
4) 32 character password that meets minimum complexity requirements

Criteria for a five-year cycle
1) All above, plus…
2) Account is also not used for impersonation, batch processing, or process automation
3) Password vault only accessible to domain administrators
4) 64 character password that meets minimum complexity requirements

​​ ​