Released: June 15, 2026
š¬ Share your feedback and shape what's next
Case Management is in Open Beta, and your input directly shapes where it goes next. Join us in the Element451 Community to tell us what's working, request what you would like to see, and compare notes with other partner schools rolling it out alongside you.
Case Management is now in Open Beta for all partners on the Student Success package. It is Element451's native student success module for catching risk signals early and managing the follow-through to resolve them, built around two connected features: Alerts and Cases.
Alerts capture one-time signals that may need attention, while Cases organize the ongoing, owned work to resolve a student issue over time. Bolt AI reads each case and recommends next steps, and built-in automation routes work to the right person. As an Open Beta, it is live and actively evolving based on partner feedback.
Alerts: Lightweight, event-driven flags that something happened and may need attention, such as a grade drop, attendance concern, wellbeing check-in, engagement dip, or financial flag.
Reviewer: Each alert is assigned a reviewer, responsible for triaging.
Resolution paths: An alert can be dismissed, resolved, or escalated into a Case when ongoing work is needed.
Triage views: Pre-built views include Triage, Unassigned, Your Alerts, Your Team Alerts, and All Alerts.
Cases: Stateful, owned records that track the work to resolve a student issue over time; a student can have multiple active cases at once.
Assignee and subscribers: Each case has one assignee who owns it, plus subscribers who follow along for updates.
Container model: Related Alerts, Appointments, Bolt Agent Jobs, Conversations, Documents, and Tasks attach to a case while remaining accessible from their source modules.
Custom status workflows: Configure custom statuses mapped to system states (To Do, In Progress, Resolved, Cancelled).
Case privacy: A privacy flag hides sensitive cases from everyone except the assignee, creator, and users with permission to view all cases.
Bolt AI Analysis: A briefing on every case that pulls together grades, engagement, past outreach, and everything linked to the case into a plain-language summary, then recommends ranked next steps with one-click actions.
Automation: Case Management offers two complementary automation engines, so teams can handle routine Alert and Case work without manual effort.
Automation Rules (new): A dedicated engine built specifically for Case Management, found in Case Management Settings with separate pages for Alerts and Cases. Each rule follows a Trigger, Conditions, Actions pattern and fires when an Alert or Case is created to route records, assign reviewers or assignees, set priorities, escalate Alerts to Cases, create follow-up tasks, enroll in a Bolt Agent Job, and more.
Workflows and Rules: Case Management is connected to Element451's platform-wide Workflows module. Alert Created and Case Created triggers enroll contacts in workflows, while Create Alert and Create Case actions generate records from any workflow, powering cross-platform automation such as student communications and engagement journeys.
Network Role token: When assigning reviewers or assignees through automation, a Network Role token dynamically routes records based on a student's assigned network role, for example sending grade alerts to that student's Academic Advisor. A Contact Assignee token routes to whoever already owns the contact.
Alert and Case Templates: Custom pre-configure templates that apply predefined field values to alerts or cases for both manual and automated creation.
Segment filtering: Build targeted audiences by filtering segments on alert and case data such as type, priority, status, and assignee.
Insights and reporting: Case Management analytics are built into two Insights dashboards, alongside existing enrollment, attendance, and grade data.
Student Success Dashboard: Student-level activity, including open Alerts and Cases, average days to resolution, and an alert-to-case Escalation Funnel, with breakdowns by type, priority, team, and status.
Management Dashboard: Staff-level activity for team leads, including assignments, resolution and on-time rates, overdue work, and where team capacity is constrained.
Portal: A dedicated, lightweight space where faculty and staff can submit Alerts and track the status of the Alerts they have raised, without access to the full Element451 platform, Cases, or settings.
Permissions and visibility controls: Layered controls determine who can see and act on each Alert and Case, and a user must pass every applicable check.
Permission levels: Alerts and Cases each have four levels: Access (view only), Manage My, Manage My Team, and Administer.
Type visibility: Set at the permission group level to control which Alert and Case types each group of users can see.
Contact visibility groups: Users limited by visibility groups only see Alerts and Cases for students within their scope.
Private cases: A private Case is invisible to everyone except its creator, assignee, and users with the View All Cases permission; even administrators cannot see it without that permission.
š§ Coming during the open beta
Open Beta is live today and will keep evolving on the way to general availability. A few capabilities are still in development and not yet included:
Timeline (Activity Feed): A chronological, event-by-event history on every Alert and Case for auditing and handoffs.
Import, Export, and API: Bulk import and export of Alert and Case data, plus a public API and external IDs for integrating with third-party systems.
Case Manager Copilot: A context-aware Copilot for case workers, with Case Management and Student Success shortcuts built into the sidebar.
Portal Enhancements: Continued refinement of the Portal, including limiting each user's student list to only the students they are related to via course enrollments and network roles.
Case Management closes the gap between noticing a student is struggling and making sure the right person acts in time. Advisors, success coordinators, and care-unit staff get a structured way to triage signals, own the follow-through, and let Bolt and automation handle the legwork, so fewer students slip through without consistent, accountable follow-up.
