Help CenterInsights – Linking Dashboards to Modules
The Link Dashboards to Modules feature allows administrators to define which dashboards are displayed by default inside different operational modules of the platform.
This ensures that users have immediate access to the most relevant analytics and visualizations based on where they are working (e.g., Projects, Timesheets, Sales, HR).
Dashboards may be assigned at two levels:
-
Tenant Level → Dashboards visible to all users in the module
-
User Level → Dashboards assigned to individual users, overriding tenant defaults
This article explains how to configure these associations.
Access Path
Insights → Dashboards → Tenant / User
1. Purpose of Linking Dashboards
By linking dashboards to modules, organizations can:
- Provide contextual analytics directly inside each module
- Standardize reporting across teams
- Reduce navigation time
- Ensure users see dashboards relevant to their role
- Support user-specific exceptions (e.g., managers get enriched dashboards)
2. Landing Page
The landing page displays two options:
| Option | Description |
|---|---|
| Tenant | Define global module-dashboard mappings applied to all users in the tenant. |
| User | Define personalized dashboard mappings for specific users only. |
3. Tenant Dashboard Mapping
Selecting Tenant opens the configuration page where administrators can define which dashboards appear in each module for every user.
Available Fields
| Field | Description |
|---|---|
| Profile | Name of the tenant profile being configured (e.g., Home Panorama). |
| Module | List of modules that support embedded dashboards (Timesheet, Project, Sales, etc.). |
| Dashboard | Dashboard that will appear when users open the selected module. |
| Add New | Adds a new module–dashboard pair. |
Behavior
-
Each module can have one or more dashboards linked.
-
If a module is not configured, it will not show dashboards by default.
-
Tenant-level mappings apply to everyone unless user-level rules override them.
4. User Dashboard Mapping
Selecting User allows administrators to customize dashboards for an individual user.
The Select User option allows users who have permission to access Insights → Dashboards → User to assign and customize dashboards for their own user profile.
Fields
| Field | Description |
|---|---|
| User | The user for whom custom mappings are being defined. |
| Module | Module where the selected dashboard will appear. |
| Dashboard | Dashboard assigned specifically to that user. |
| Add New | Adds additional module–dashboard relationships. |
Behavior
-
If a user has a mapping for a module, it overrides the tenant-level configuration for that module.
-
If a module is not mapped for the user, the system defaults back to tenant-level rules.
5. Actions
Both Tenant and User pages support:
| Action | Description |
|---|---|
| Save | Saves all module-dashboard mappings. |
| Cancel | Discards unsaved changes. |
| Add New | Adds a new mapping entry. |
6. Examples
Example 1 – Assign dashboards to all users (Tenant)
| Module | Dashboard |
|---|---|
| People Management | People |
| Project | Projects Cockpit |
Result: All users see the People dashboard in Timesheets and Projects Cockpit in the Project module.
Example 2 – Give a manager a custom dashboard (User)
| Module | Dashboard |
|---|---|
| Project | Management Overview |
Result:
All users → Projects Cockpit (Tenant rule)
Manager → Management Overview (User override)
7. Recommendations
- Define a global tenant baseline first to ensure consistency.
- Use user-level overrides only when necessary (management roles, specialized dashboards).
- Regularly review mappings after dashboard changes.
- Ensure dashboards are shared with the appropriate users; otherwise, they cannot be displayed.