Knowledge is moving to Halo
The Knowledge Base is a library of help articles our community can find, follow, improve and share
Knowledge at work
The Halo Knowledge Base is being released on November 30, 2026. All IT agents will start seeing suggested knowledge articles while working on tickets in Halo. This release marks the first phase of York’s Knowledge-Centered Success (KCS) rollout. Halo agents will begin using knowledge as part of everyday support. Pilot participants will also create and improve articles, helping us refine our process, content standards and support before authoring expands to more teams
Find use link and share
Search for what we already know. Use relevant knowledge, link the article that helped with the ticket and share suitable guidance with the requester. Give feedback when something needs attention
Follow the non-pilot KCS guideCreate and improve
Build on those shared habits by creating and updating knowledge during live support work, within your training and permissions. Bring real examples to coaching and help improve the practice
Find pilot resourcesLaunch & Adopt
-
1
November 30, 2026
Production release
Knowledge becomes available in Halo and IT agents will begin to see suggested articles popping up with associated tickets
-
2
November 30, 2026 - May 2027
Pilot phase
Pilot participants begin working using KCS practices in live support work and help us improve our Knolwedge management permissions, materials, content standards and support before wider adoption
-
3
May 2027
Adopt in waves
As our knowledge practice matures, we'll strengthen validation, coaching, roles and measures and onboard frontline teams in waves based on readiness and capacity
-
4
Summer 2027
Enable self-service
After we solidfy our foundation and hone our knowledge creation and maitenenace skills, we'll enable community-wide self-service for polished and published knoweldge articles
Knowledge is...
Connected to our services
Knowledge articles will be associated with the services they support and the work they were created to solve. Metrics will link our most essential knowledge to our most requested services and vice versa.
Shared with the right people
Articles can be available to all IT agents or limited to specific Halo support queues (teams). A team-specific SOP or KA can stay within that team, while something like DUO Reset instructions can be available to every agent, and, in the future, every member of the York community.
Used in the flow of work
"Have you tried turning it off and on again?" Shared articles can be used while resolving a ticket and sent directly to the requester, giving agents a fast, consistent library of reusable responses that saves them rewriting the same instructions over and over... and over.
Expanded in waves
Creating and editing knowledge will remain limited to approved Halo agents who have completed KB onboarding. After the pilot, more teams will gain these permissions as they join future KCS adoption waves.
Published for self-service
After the pilot and wider frontlin eonboarding, approved knowledge can begin moving to the self-service portal so students, faculty and staff can find and follow trusted answers themselves.
Agent expectations
On launch, all IT agents will be able to use the knowledge base, but only the pilot group will create and udpate knowledge.
Read and share knowledge
Search for relevant knowledge while working on tickets
Use trusted articles to help resolve tickets and use Send with Next Action to share helpful resolutions with requestors
Creating or editing knoweldge will become available as we onboard new teams to our evolving KCS standards
Create and update knowledge
Update useful articles when something is missing, unclear or out of date
Create knowledge when no suitable article exists and the answer is likely to help again
Solve once
Share always
Our Knowledge Base turns the work we solve every day into knowledge everyone can reuse. Agents get to answers faster, our community gets more opportunities to self-serve, and future AI and automation have a trusted source to work from
Reuse what already works
Start with proven answers instead of investigating and documenting the same problem again
Help people help themselves
Build trusted answers that students, faculty and staff can increasingly find and use without contacting support
Unlock AI
Keep the creation and improvement of knowledge with staff, so future tools are built and controlled by a trusted and maintained source
Knowledge in every interaction
KCS makes one simple habit part of support work: look for what we already know first, then improve or add to it when the work teaches us something new
-
01
Search
Search early, then refine as you understand the issue
-
02
Reuse
Use and link the best available article when it helps
-
03
Improve
Fix useful knowledge when it is incomplete or out of date
-
04
Create
If no useful article exists, pilot participants create one when the answer is likely to help again
-
05
Ask
If access, ownership or content is unclear, use the pilot support path
FAQs
Does everyone need to start writing articles on November 30?
No. Everyone can search and use knowledge, but only the pilot group is able to, and expected to, create and improve articles at launch
What if an article exists but needs work?
Improve it by creating a new version if your role and permissions allow. If you don't have permission, use a thumbs down to provide feedback that something needs to change. If you spot something that urgently needs to be changed, reach out to the article owner, or submit a ticket to askIT@yorku.ca to request an update
