​

Customizable Landing Page with Pluggable Panels

Collate’s customizable landing page allows admins to tailor the layout based on the user’s persona, providing a more relevant and enriched experience. The landing page is built using pluggable panels, which can be added, removed, or rearranged to meet the unique needs of different personas, such as data scientists, data engineers, or data stewards.

​

Customize App Layout

Use the Customize UI tab on a persona to set the app mode, default landing page, and default views for every user assigned to that persona. To open these settings:

1. Navigate to Settings > Personas.
2. Select a persona.
3. Click the Customize UI tab.

4. Click the App Layout card.

The App Layout card opens the Customize App Layout page. It has three settings for this persona: App Mode, Default Landing Page, and View Mode. After you change a setting, click Save. Click Reset to discard your changes.

​

App Mode

Choose the default experience users of this persona see when they log in. A user’s own app mode choice takes priority over the persona setting.

• No default: Falls back to the organization default.
• Classic: The standard catalog experience, with a My Data, Domain, and My Tasks home page. Use this when a team prefers the pre-2.0 experience or relies on Classic-only widgets.
• AI: Starts in the AI assistant, with the Collate 2.0 home page and AI-powered dashboard: Platform Health, Action Required, Recommended Improvements, Pending Approvals, and more. Recommended for most personas in Collate 2.0.

​

Default Landing Page

Use Default Landing Page to choose where users of this persona land when they open the app. The default is Home (My Data). Select one of the following pages from the dropdown:

• General: Home (My Data), Explore, and Lineage.
• Data Marketplace: Data Marketplace, Domains, and Data Products.
• Observability: Data Quality, Incident Manager, and Insights.
• Govern: Glossary, Classification, and Metrics.

Collate sends users to this page only when the app first opens, such as after sign-in, after a page reload, or in a new browser tab. A deep link that a user opened before signing in takes priority. Later visits to the home page inside the app, such as clicking the logo, are not redirected.

​

View Mode

Use View Mode to set the starting view for pages that offer more than one layout. Pages without a setting open in Table view. To set a starting view, click Add Page, select a page, and choose its view:

• Domains: Table, Grid, or Tree.
• Sub Domains: Table or Grid.
• Data Products: Table or Grid.
• Learning Resources: Table or Grid.

Users can still switch the view on the page.

​

How to Customize a Landing Page:

1. Set Up Personas: After defining personas, navigate to Settings > Persona.

2. Select a Persona: Customize a landing page for a specific persona (e.g., data steward) and then select homepage to customize it.

3. Click on Add widget

3. Pluggable Panels: Configure panels based on the needs of each persona by adding widgets as required and then click on apply. Panels can include:
   • Activity Feed
   • Key Performance Indicators (KPIs)
   • Recent Announcements
   • Tasks
   • Recently Viewed and more

4. Rearrange and Save: Adjust the layout based on user preferences and save the configuration.

​

Example Use Case:

For a data scientist, the KPI panel may be removed, while prioritizing recent announcements and recent views. A data engineer might add a Pipeline Status panel, while a data steward might include panels focused on data governance.

​

Future Enhancements:

Additional panels, such as Data Quality Status or Knowledge Articles, can be added to further personalize and enhance the user experience. By leveraging pluggable panels, the customizable landing page can be tailored to enrich each user’s experience, making the platform more relevant and effective for different personas.

​

Switching Between Personas

Users can switch between different personas without logging out or reconfiguring the platform. Upon switching, the application’s landing page and configuration adjust automatically to reflect the new role.

​

Setting a Default Persona:

Users can set a default persona, so the system displays the layout and settings relevant to that role every time they log in.

​

Use Case Examples:

​

1. Data Engineer

• Needs: Data pipeline monitoring, data quality, and task management.
• Customized Landing Page: Includes panels for pipeline status, data quality metrics, and recent tasks related to pipeline execution. Announcements and Insights KPIs might be deprioritized.
• Persona-Specific Panels: Add a Pipeline Status panel for real-time updates on data workflows.

​

2. Data Steward

• Needs: Access to recent data views, performance indicators, and analysis tools.
• Customized Landing Page: Prioritizes recent data views and KPI dashboards, while removing unnecessary panels such as pipeline status.
• Persona-Specific Panels: Data stewards might add panels related to KPIs or recently viewed data assets.

​

Future Customizations:

Collate plans to expand persona-based customization beyond landing pages to entity pages as well. For example:

​

1. Entity Pages Customization:

Users can add panels that display specific metadata, such as product-related knowledge articles or glossary terms associated with an entity.

​

2. Knowledge Panel Expansion:

Additional panels like Product Knowledge Articles or Service Status will allow deeper insights based on the user’s role.