Custom dashboards give student success staff a focused view of student context on the person record. A useful dashboard helps staff answer immediate questions, understand recent activity, and decide what follow-up belongs next.
Start with the same practical test used in Custom Dashboards for Student Success: if the student walks into the office, what information should staff know immediately? The answer is usually a small set of well-chosen data points, not every field available on the record.
Guiding principles
Use these principles to keep each dashboard focused and maintainable:
Role fit: Design each dashboard for the staff who will use it.
Immediate context: Prioritize the information staff need before an appointment, outreach attempt, or case review.
Source-backed signals: Show the data behind any summary, alert, or AI-generated recommendation.
Permission awareness: Limit dashboard content to data the audience should see and act on.
Maintenance: Keep ownership clear so dashboard content stays current as processes change.
Step 1: Defining the dashboard audience
Start with the staff role and the moment of work. A dashboard for an advisor preparing for an appointment will differ from a dashboard for a retention manager reviewing open follow-up.
For each dashboard audience, define:
The users who should see the dashboard
The decisions the dashboard should support
The fields or panels that should be hidden by permission
The action staff should be able to take after reviewing the dashboard
Action item: Review Dashboards for Student Success before choosing the first dashboard audience.
Step 2: Choosing dashboard content
Build the dashboard around the information staff need most often. Keep the first version narrow, then add content only when staff can explain how they will use it.
Useful dashboard content often includes:
Student context: Program, term, status, and other high-value record details
Ownership: Assigned advisor, success coach, or team owner
Engagement: Recent communication, appointment history, and important milestones
Open work: Active tasks, cases, alerts, or checklist items that require follow-up
Use separate dashboards or conditional display logic when different audiences need different content. That keeps each view smaller and reduces the chance that staff see information outside their role.
Step 3: Building the dashboard query
Dashboard content comes from a query. The exports in the query become merge fields in the dashboard editor, so each export name must be friendly to Liquid markup: lowercase, short, and free of spaces.
Use filters to control which records appear on the dashboard. Use Liquid markup and existence exports when a dashboard section should appear only when data exists.
Action item: Use the dashboard setup guidance in Dashboards for Student Success while naming exports and configuring filters.
Step 4: Adding AI dashboard guidance
AI Dashboards use the exports in the dashboard query as context. Those exports define the AI dashboard's scope, so the prompt should ask for analysis based only on the data supplied to the dashboard.
When adding AI dashboard content, define:
Context: The exports that the AI dashboard should interpret
Instruction: The kind of summary or recommendation the output should provide
Review path: The source details staff can check before taking action
Dashboard signal | Useful dashboard response |
|---|---|
Missed appointment or recent inactivity | Show the last touch, assigned owner, and a scheduling path. |
Open case or unresolved alert | Show the owner, due date, and current workflow status. |
Registration or hold issue | Show the relevant office, staff owner, and follow-up instructions. |
Conflicting indicators | Show the source data so staff can review the record before prioritizing outreach. |
Do not use AI output for priority decisions unless the dashboard also shows the source exports or explanation staff should review.
Step 5: Connecting dashboards to daily work
A dashboard is most useful when staff can move from context to follow-up without rebuilding the same search elsewhere.
Connect dashboard content to related work surfaces:
Use Assignment Lists for user-scoped lists of assigned students who need action.
Use Workflows when dashboard signals should feed a consistent review or follow-up process.
Use Scheduler when the next action is an appointment with the assigned staff member.
Keep the dashboard focused on orientation and decision support. Move longer procedures, queues, and case management into the Slate tool built for that work.
Step 6: Testing and maintaining the dashboard
Test each dashboard with the roles and records staff will use in daily work. Administrative accounts often hide permission issues that staff will encounter after rollout.
Before launch, confirm:
The dashboard appears for the right records
Each merge field resolves to the expected data
Role-based access hides restricted information
AI dashboard output stays inside the supplied query context
Staff know who owns future dashboard changes
Review dashboard adoption after launch. Remove unused panels, revise noisy signals, and add only the content that improves daily work.
Recommendations
A strong student success dashboard helps staff see the right context at the moment they need it.
Start with one audience: Build a focused advisor or coach dashboard before expanding to other groups.
Keep export names stable: Changing export names can break merge fields in the dashboard editor.
Test with non-admin roles: Confirm that the dashboard works for the staff who will rely on it.
Connect context to action: Use related tools for assignments, workflows, appointments, and follow-up.
Review regularly: Dashboards should change when the student success process changes.