When creating sample reports to be used on the dashboard, what is a good practice to follow?

Charting functionality is a core feature of dashboard reports and avoiding it would reduce the visual effectiveness and analytical value of the dashboard.

There is no standard requirement to create exactly 5 reports per application - the number should be driven by customer requirements, not an arbitrary minimum.

Duplicating customer-provided sample reports is best practice because it mirrors the real-world reporting requirements the customer has already validated and uses in their environment. This approach reduces miscommunication and ensures the dashboard reflects familiar, meaningful data views. It also accelerates configuration by leveraging existing report structures rather than building from scratch.

Restricting reports to only the sample end user account defeats the purpose of dashboard reporting, which should be accessible to appropriate roles across the organization.