Review security for public Confluence articles
- Denise Kidd
Problem statement
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.
Review all articles and adjust security on articles with content we don’t want used to answer chatbot questions.
Stakeholders with marginalized identities
Stakeholder feedback
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 |
|
Review all articles and adjust security on articles with content we don’t want used to answer chatbot questions.
Denise Kidd, Nicole Westerfield
ID numbers should never be released via ticket, phone, or email. Students can access their ID numbers via Gibson. Students needing ID numbers for transcript orders can enter their SSN or 9 0's in the ID number field.