We are preparing to implement Ocelot, which allows us to deploy an AI chatbot to answer our most-asked questions and connect students with specific aspects of their student record. Ocelot can “read” any source we identify, so to be prepared, we need to review all of the public articles in Confluence to determine which we want to be ready by Ocelot.
Job story
When_____, I want to _____, so I can _____.
When we implement Ocelot, I want to restrict pages from public view to prevent unrelated or inappropriate content from being used to answer questions.
Current process
Currently, all but a handful of Confluence articles in our public space are public.
Objectives
Review all articles and adjust security on articles with content we don’t want used to answer chatbot questions.
Stakeholders
Stakeholders with marginalized identities
Stakeholder feedback
Scope
In Scope
Out of Scope
Student curriculum maintenance training
Admissions
Registrar tools access review and management
Identify a process internal to SSE to streamline the certification process
Assigning advisors training
Proposed solution
Review all articles and adjust security on articles with content we don’t want used to answer chatbot questions.
Proposed process
Timeline
Research
Workgroup
Denise Kidd, Nicole Westerfield
Actions
Review all articles in the public Confluence space and change security as appropriate.