Decommissioning Area-Specific Intranets

• Content on these legacy sites is based on structures and support models that pre-date the SHA, and much of the information is outdated, incomplete or inaccurate as a result.
• The legacy sites are also hosted on platforms that are no longer supported.

No. Team collaboration SharePoint sites are not being decommissioned. Only the legacy intranet sites are scheduled to be taken offline.

However, Digital Health is in the process of upgrading these sites from SharePoint 2016 to SharePoint Online to ensure they remain modern, secure and supported.

While a formal date has not been set, relevant content will transition to one of the provincial platforms over the next few months, after which the legacy intranet sites will be taken offline. Sites will be temporarily archived following their transition, with the goal of being fully decommissioned by Q4 of the 2026–27 fiscal year.

Community Engagement and Communications (CEC) is coordinating this work with the support of Digital Health and eHealth Saskatchewan (eHS). Content owners (operational leaders) are responsible for reviewing and assessing their content, to validate and provincially coordinate the content to be kept. 

Leaders responsible for content will be asked to validate their information and determine what should transition to a provincial platform and what should be archived. Relevant content includes the information, tools and resources staff rely on to perform their work and stay informed.

Once validated, content owners will be responsible for posting to a provincial platform and maintaining it. Please note that this is not a simple copy-and-paste process. All content must be reviewed, updated and potentially rewritten within a provincial context while maintaining area-specific requirements where appropriate.

Content that is still required will transition to either:

• the SHA intranet (no login requirement); or
• a provincial SharePoint site (access restricted to those with SHA network account).*
  (* currently being developed)

The SHA intranet and provincial SharePoint sites are the recommended platforms for provincial content. Department/project-specific SharePoint sites can still be used; however, they will have unique permissions and not readily connected to a provincial platform.

No, these are separate platforms. The target audience of both platforms is health providers but the SHA intranet has no login requirement, and the provincial SharePoint is restricted to those logged into the SHA network.

• Content will not automatically transition to a provincial platform.
• Leaders responsible for content will be required to validate relevant information that should transition to a provincial platform.
• Content identified as no longer relevant will not transition and ultimately be taken offline.

The provincial SharePoint site access is restricted to those logged into their SHA network account.

Temporarily archived content will be deleted after approximately three months.

• Relevant content that does not require restricted access can be added to the SHA intranet. Please see the Adding Website Content page for more information.
• Content requiring restricted access must wait for the provincial SharePoint site to be developed but work to prepare that content can begin immediately.

Please speak with your leadership regarding legacy site content.

Please connect with your leaders if you cannot find the content you need.

Development of the site’s design and navigation is currently in progress and more information will be shared as it is available.

No, the appearance will differ because the provincial platforms will follow specific presentation standards and offer a more modern, streamlined interface.

• The model of support for the provincial SharePoint site is still being considered; however, please discuss your need/desire to edit the site with your leader.
• For the SHA intranet, departments/portfolios are asked to identify at least two Content Editors to manage their content.

Extensions cannot be granted as legacy intranet content is based on structures and support models that pre-date the SHA, and much of the information is now outdated, incomplete or inaccurate.