Create a custom Dashboard Portal to display a tailored default view on person records. A Dashboard Portal can surface high-priority profile details, advising information, materials, tabs, and query-driven tables without requiring users to move between several record tabs.
Try a Slate example 💼
Copy this Suitcase ID and paste it in Database → Suitcase Import to import an example dashboard portal:
4b28212e-f3d4-4938-834e-dc8c81b917ef:slate-success-showcase⭐ Get Inspired
This article was adapted from a post by Technolutions staff in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? Let us know!
Creating the portal
Go to Database → Portals.
Create an Express Portal for the student record dashboard.
Set the portal scope to Person.
Set the security type to User.
Enter a unique portal key.
Building the default view
The default view can combine static HTML, CSS, Liquid Markup, portal queries, and materials. In the example, the dashboard includes a headshot, student details, tabbed sections, and collapsible tables.
Use portal queries to return the data that should display on the dashboard. Keep those queries focused so the dashboard loads quickly and only displays information that helps users take action.
Connecting the portal to records
After building and testing the portal, configure the standard profile tab settings so the Dashboard tab displays the custom portal.
Preview the portal with several test records.
Confirm that all queries return the expected data for users with the intended permissions.
Confirm that the dashboard works for records with missing optional data, such as no headshot or no recent activity.
Update the profile tab setting to use the custom dashboard portal.
⭐ Best practice
Use a test environment before replacing a standard record dashboard, especially when the portal includes several queries or permission-sensitive data.
For more information, see Modifying Standard Profile Tab Settings.