OVERVIEW
This page tracks the state of migration from SFU Maillist to SFU Groups for SFU applications.
DETAILS
This page tracks the migration of some SFU applications from using SFU Maillist to SFU Groups. This is not an exhaustive list of SFU applications. The information on this page is provided by individual service owners. If you have questions about a specific service's plans for migrating from SFU Maillist, please contact that application's designated support contact.
If you are a service owner and would like to have your application added to this page, or information updated, please open a ticket.
| Service Name |
Status |
More Information / Steps Required |
Support / Contact |
| Adobe Experience Manager (AEM) |
Target: December 11, 2024 |
AEM team has contacted site owners with steps required to migrate from Maillists to SFU Groups |
AEM support |
| ServiceHub |
Unknown |
Unknown |
ServiceHub support |
| Canvas non-credit enrolments |
Unknown |
Non-credit courses can have enrolments driven by maillist memberships. |
Canvas support |
| Amaint |
In-progress |
Departments with access to Amaint will be required to provide reference groups to maintain access |
ITS Identity Management group |
| Microsoft Teams |
Done |
- Existing Teams must be updated with reference groups using the Teams Request page
- New Teams requests must provide reference groups instead of Maillists
|
MS Teams support |
| SFU GitHub |
Done |
- Existing maillist-backed GitHub Organizations must be updated with reference groups for organization users and admins.
- New GitHub Organization requests must provide reference groups for organization users and admins.
|
Open a ticket to update existing organizations |
| Tableau |
Done |
|
Tableau support |