Understanding Dashboard Priority and Visibility

When a user has access to multiple Dashboards, Learn Amp determines which Dashboard to display first based on a priority hierarchy. Understanding this system helps administrators design effective Dashboard strategies that ensure users see the most relevant content immediately upon login.

The priority system considers the user's role, team memberships, manager status, and onboarding period to automatically select the most appropriate Dashboard.

When a user accesses the platform, Dashboards are evaluated in this order (highest priority first):

The first Dashboard found at the highest priority level with "default" status becomes the user's default Dashboard.

Personal (Manager) Dashboards

• Created by individual managers for their own use

• Only visible to the manager who created them

• Appears first if Manager Dashboards are enabled

• Sorted alphabetically, with manager's default Dashboard first

Onboarding Dashboards

• Shown to users within their defined onboarding period

• Based on days_after_start_date setting

• Can optionally remain visible after onboarding period ends

• Takes priority over other Dashboard types during onboarding

Manager Type Dashboards

• Targeted at specific manager types:

  • Primary Team Manager

  • Secondary Team Manager

  • Override Manager

  • Stand-in Manager

• Each manager type can have different visibility and default settings

Team Dashboards

• Assigned to specific teams

• Users in primary teams see these before secondary team Dashboards

• Team settings determine visibility and default status per team

Role-Based Dashboards

• Traditional role-based assignment (Learner, Curator, Reporter, Admin, Owner)

• Lowest priority in the hierarchy

• Sorted alphabetically, with default Dashboard first

Each Dashboard has two important settings:

A Dashboard can be visible but not default—the user can navigate to it but won't see it first.

To configure Dashboard priority and visibility:

• You need Owner or Admin access

• Audience-specific Dashboards (Onboarding, Manager Type, Team) must be created with appropriate settings

1. Navigate to Settings in the sidebar, then select Dashboards

2. Find the Dashboard you want to make default

3. Click the three dots menu and select Edit Dashboard

4. In the visibility section, find the role you want to configure

5. Tick both Visible and Default for that role

6. Save your changes

⚠️ Warning: Only one Dashboard can be default for each role. Setting a new default will remove the default status from the previous Dashboard.

1. Navigate to Settings in the sidebar, then select Dashboards

2. Click Create Dashboard

3. Set Audience type to Onboarding

4. Configure the Days after start date (how long users see this Dashboard)

5. Optionally enable Visible after onboarding to keep the Dashboard accessible after the onboarding period

6. Add appropriate widgets for new starters

7. Save and publish

1. Create a Dashboard with Audience type set to Team

2. Select which teams should see this Dashboard

3. For each team, configure:

   • Visible: Team members can see the Dashboard

   • Default: This Dashboard loads first for team members

4. Save your changes

Goal: Show a welcome Dashboard for the first 30 days, then switch to the standard Dashboard.

1. Create an Onboarding Dashboard with:

   • Days after start date: 30

   • Visible after onboarding: No

   • Widgets: Welcome message, To-do List, Assigned Channels

2. Create a Role-Based Dashboard with:

   • Visible and Default for Learner role

   • Widgets: Standard learning content

Result: New users see the Onboarding Dashboard for 30 days, then automatically see the standard Dashboard.

Goal: Managers see their reporting Dashboard before the standard learner Dashboard.

1. Create a Manager Type Dashboard with:

   • Target: Primary Team Managers

   • Visible and Default enabled

2. Ensure the standard Role-Based Dashboard is also visible to managers

Result: Managers see their reporting Dashboard first, but can switch to the learner Dashboard if needed.

Goal: Marketing team sees a different default Dashboard than Engineering.

1. Create a Team Dashboard for Marketing team:

   • Visible and Default for Marketing team

2. Create a Team Dashboard for Engineering team:

   • Visible and Default for Engineering team

3. Create a general Role-Based Dashboard as fallback

Result: Each team sees their specific Dashboard first.

Q: What happens if a user matches multiple Dashboard types?
The priority hierarchy determines which Dashboard appears first. A user in an onboarding period who is also a manager would see the Onboarding Dashboard first (priority 2) rather than their Manager Dashboard (priority 3).

Q: Can a user override the default Dashboard?
Users can navigate to any visible Dashboard using the Dashboard selector. However, the system default will always load first when accessing the platform.

Q: What if no Dashboard is set as default for a user's role?
The system will show the first visible Dashboard found at the highest priority level, sorted alphabetically.

Q: How does the "visible after onboarding" setting work?
When disabled, the Onboarding Dashboard disappears from the user's Dashboard list after their onboarding period ends. When enabled, they can still access it but it won't be their default anymore.

Q: Can I have different defaults for different teams?
Yes. Each team can have its own default Dashboard configured in the Team Dashboard settings.

Q: What about users in multiple teams?
Primary team Dashboards take precedence over secondary team Dashboards.