We want to inform you about upcoming changes to our ArgoApps service, which will take effect in 2024. ArgoApps is a valuable resource for our faculty, staff, and students, and we're continuously working to improve the service to meet the evolving needs of our community.
Change Effective Date: January 1, 2024
What's Changing?
Starting on January 1, 2024, access to ArgoApps will transition from automatic access to a request-based system. This means that faculty, staff, and students will no longer have immediate access to the service. Instead, users will need to submit a request to gain access.
In addition, we would like to inform you that after 6 months of inactivity, user access to ArgoApps will be automatically removed. This change is part of our efforts to maintain security and resource efficiency within the service.
Why Are We Making These Changes?
We are implementing these changes to ensure that ArgoApps remains a secure and reliable resource for our community. By moving to a request-based system and removing inactive accounts, we can better manage user access, monitor usage, and allocate resources more effectively. This change will help us provide a seamless and consistent experience to all users.
Who Does This Change Apply To?
All users who have used ArgoApps in the past as well as new users must request access in order to use ArgoApps starting January 1, 2024.
How to Request Access
To request access to ArgoApps, simply follow these steps:
- Submit an access request via ArgoApps Access Request or by the MyUWF app 'ArgoApps Access Request'.
- If prompted, log in with your ArgoNet credentials.
- Read and understand the ArgoApps Usage Agreement to which you will need to agree to proceed with your request.
- If you agree with the terms and conditions, click the 'I agree' button, and submit your access request.
Approval is typically granted within minutes, and you will receive an email notification when your access request is approved. However, please note that it may take up to 30 minutes after approval for you to have access to ArgoApps.
By submitting your access request, you acknowledge that you have read and agree to comply with the ArgoApps Usage Agreement (found below).
ArgoApps Usage Agreement
ArgoApps are hosted apps & virtual lab computers that allow UWF students, faculty, and staff to access specialized computer apps via the Internet.
Optimal ArgoApps performance requires a high-speed internet connection.
ArgoApps can be used with either a web browser or an installed application, Citrix Workspace. Compare the differences between the web browser-based method, known as "ArgoApps Lite," and the Citrix Workspace App.
ArgoApps shall be used in pursuit of the University’s mission, goals, policies, and procedures. Computing resources shall not be used for personal financial gain or for commercial purposes not under the auspices of the University. Some apps are licensed for academic coursework use only.
You will be disconnected after 30 minutes of inactivity and automatically logged off after 60 minutes of inactivity. Any unsaved information may be lost!
It is your responsibility to save your data when using ArgoApps. Suggested locations are your UWF Google Drive or your personal computer. Visit ArgoApps Help to learn more about saving files and using ArgoApps.
Access will be removed after 6 months of inactivity.
FAQs
We understand you may have questions about these changes. Here are some common FAQs to address your concerns:
Q: Why are you implementing these changes?
A: We are making these changes to enhance security, resource management, and the overall user experience for ArgoApps.
Q: Will the service still be available to faculty, staff, and students
A: Yes, ArgoApps will remain accessible to faculty, staff, and students; access will just be granted through a request process.
Q: How will you define account inactivity?
A: Account inactivity is defined as no logins or usage of ArgoApps for a continuous period of 6 months.
Q: What happens if my access is removed due to inactivity?
A: If your access is removed, you may request access again through the request process.