Supporting Material Attached to the Student Case
This connector is not prebuilt. It would be built to your requirement on the REST API and ingestion path the platform already uses, with scope and effort agreed per engagement. Navigate360 is a student success platform for advising, alerts and retention case management. Its records are case notes about people, which makes this the most access-sensitive connection in the education set and changes what is worth building.
How it connects
Advising records and case notes would come across over the API, the case reference arriving as an attribute so supporting material files against the right student case. Supporting material here is usually a recorded advising session, a workshop recording, or a document that belongs to an intervention.
Access is the whole design. An advising case is visible to the advisor working it and to whoever supervises, not to the institution generally, so the attributes that arrive have to drive access rather than merely label the item. An engagement would settle which roles see what before anything is built, and would establish whether recording an advising conversation is permitted at the institution at all, because in many it is not. That question belongs first: a connector that files recordings nobody is allowed to make has no use.
Navigate360 would stay the case system. The case and its notes stay authoritative there, and nothing is written back unless a step is scoped for it. A workflow could assemble what a case review needs, or surface material attached to cases that have been closed and should now fall under a retention decision.
What you can do together
- Attach supporting material to the advising case it belongs to, visible to the advisor and supervisor rather than to the institution.
- Keep retention on that material tied to the case rather than left open indefinitely.
- Assemble what a case review needs with a workflow reading the record.
- Surface material on closed cases so a retention decision can actually be applied.
A scenario
- ScopingThe engagement would establish whether advising sessions may be recorded at all, which roles see what, and how long material is kept after a case closes.
- SetupThe connection would be configured once against the Navigate360 API with the case reference mapped to an attribute.
- FilingA workshop recording attaches to the cases of the students referred to it, visible to their advisors.
- A case reviewA workflow assembles the material on a case for the supervisor conducting the review.
- ClosureWhen cases close, a workflow lists the attached material so the agreed retention decision is applied rather than forgotten.
What stays where
Navigate360 remains the case system
Advising, alerts and case notes stay there.
Access is scoped to the case, not the institution
Material is visible to the advisor and supervisor, which is the reason the attributes have to drive access.
Whether sessions may be recorded is settled first
It is an institutional policy question, and it determines whether the connector has a use.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud, or on premises, with a network path to Navigate360.
Products and solutions
Next step
See it on your own EAB Navigate360 instance. We will show the connection made, the data moving and the output, then size it for your deployment.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/eab-navigate360