Unity’s Una Navigator asks before changing a student record

Unity Environmental University’s [October 29 report](https://unity.edu/press‑releases/unity‑environmental‑university‑is‑writing‑its‑own‑playbook‑for‑ai‑in‑higher‑education/) describes how it uses AI for student support, including Una Navigator’s record‑based answers and requests for permission before changes. It reports an existing institutional approach, rather than announcing four newly available assistants. According to [Unity’s Navigator page](https://unity.edu/una/una‑navigator/), applicants and current students open it after signing into their own portals. The public website chat serves prospective students instead. Navigator can answer questions using the user’s Unity records. For a student trying to resolve a registration question, the entry point matters. General program information and an answer based on a personal record are different services. The practical first check is whether the user has opened the appropriate portal, rather than assuming that any university chatbot has the same context or authority. The current report should not be read as a launch date for every capability on the product page. That page explains the described service but does not provide a separate release date for each action.

Unity [lists actions that require the user’s approval](https://unity.edu/una/una‑navigator/): messaging an advisor, updating a mailing address, setting reminders and opening an IT ticket. Applicants can also change their program or start term. A useful review of a proposed change starts with the action itself. Which field would change, which person would receive a message and what request is being approved? A conversational answer about a start term is not the same thing as permission to alter it. For example, an applicant considering a later start can distinguish a question about options from a request to make an update. Before approving an action, the applicant can check that the proposed program and term match the intended request. This is a suggested way to read the documented permission boundary, not a portal transaction OpenTools performed. The same distinction applies to a message: asking the assistant for information and asking it to send information to a staff member are separate choices. The product description does not establish that every action or account situation has been independently tested.

The [product page](https://unity.edu/una/una‑navigator/) says chats are saved, a summary joins the Unity record and supporting staff can see it. It directs users to an advisor or concierge when something looks wrong or needs human attention. A handoff can therefore involve more than starting a fresh conversation with a person. A student can ask what information will be passed on, review an important detail and clarify what needs a staff decision. The retained‑summary description is useful context when deciding what to put in the chat; it should not be mistaken for a promise that the exchange is visible only to the student. These are Unity’s descriptions of its support workflow. OpenTools did not access a student account, inspect underlying records or test the system’s privacy, security or answer quality. The two pages do not establish that the approach improves retention or learning outcomes. A SOAR Cross College Advising Service session at the WisCEL Center in College Library, photographed July 18, 2017. Archival academic‑advising context; not Unity students, an Una demonstration or evidence of an AI outcome. Photo: [college.library / Wikimedia Commons](), [CC BY 2.0](https://creativecommons.org/licenses/by/2.0/). Responsive crop/downscale; photograph otherwise unaltered.