Contacts and emergencies¶
First contact should almost always be made through the UIS service desk. Their contact details are available on a UIS Intranet page. If you are not a member of UIS, we re-publish the details below but note that the intranet site is canonical:
- To log an incident contact email@example.com.
- To escalate a ticket or contact the Service Desk Manager contact firstname.lastname@example.org.
If you are a DevOps member wishing to give the service desk a "heads up", the correct contact is email@example.com.
The remaining contact details should ordinarily only be used by the service desk when escalating an incident. Please do not attempt to circumvent the process by emailing us directly.
We have some service-specific contact addresses which should be used when contacting us about the corresponding service:
- GitLab support requests should be raised as an issue on the support project in GitLab. Should you need to email the GitLab operations team directly, you can used firstname.lastname@example.org.
- Email about the legacy git.uis service should be directed to email@example.com.
- Support requests for Raven should be sent to firstname.lastname@example.org. The Raven admin team can be contacted directly in an emergency via email@example.com.
- Cloud computing (Amazon, Google, Azure, etc) related issues should be reported in the first instance to firstname.lastname@example.org. Email threads which the Cloud team should be aware of should be Cc-d to email@example.com
- G Suite@Cambridge related issues should be reported in the first instance to firstname.lastname@example.org. Email threads which the G Suite team should be aware of should be Cc-d to email@example.com
- Lookup issues should be sent to firstname.lastname@example.org. Only issues of a technical nature should be escalated to email@example.com.
You can send us GPG encrypted files or email by using our GPG public keys.
The generic email address for the team is firstname.lastname@example.org.