<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Best practices and ways to organize dashboards in Dashboarding</title>
    <link>https://community.dynatrace.com/t5/Dashboarding/Best-practices-and-ways-to-organize-dashboards/m-p/304433#M5895</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;In our organization, we manage a large number of dashboards and would like to establish proper governance and control over them.&lt;/P&gt;
&lt;P&gt;Our objective is to have clear standards not only for dashboard naming conventions, but also for aspects such as organization, ownership, permissions, lifecycle management, and overall governance.&lt;/P&gt;
&lt;P&gt;For example, in other platforms we use mechanisms such as &lt;STRONG&gt;Spaces&lt;/STRONG&gt; in Kibana and &lt;STRONG&gt;Organizations&lt;/STRONG&gt; in Grafana to structure and manage dashboards at scale.&lt;/P&gt;
&lt;P&gt;Are there any official guidelines, best practices, or community recommendations regarding:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Dashboard naming conventions&lt;/LI&gt;
&lt;LI&gt;Foldering or organizational strategies&lt;/LI&gt;
&lt;LI&gt;Access control and permissions regarding create and read dashboards.&lt;/LI&gt;
&lt;LI&gt;Ownership and accountability&lt;/LI&gt;
&lt;LI&gt;Dashboard lifecycle management (creation, review, deprecation, retirement)&lt;/LI&gt;
&lt;LI&gt;Governance models for large-scale dashboard environments&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Any documentation, experiences, or recommendations from other Dynatrace users would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thank you very much for your support.&lt;/P&gt;
&lt;P&gt;Best regards.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 17 Sep 2026 05:50:02 GMT</pubDate>
    <dc:creator>FranciscoMPalos</dc:creator>
    <dc:date>2026-09-17T05:50:02Z</dc:date>
    <item>
      <title>Best practices and ways to organize dashboards</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Best-practices-and-ways-to-organize-dashboards/m-p/304433#M5895</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;In our organization, we manage a large number of dashboards and would like to establish proper governance and control over them.&lt;/P&gt;
&lt;P&gt;Our objective is to have clear standards not only for dashboard naming conventions, but also for aspects such as organization, ownership, permissions, lifecycle management, and overall governance.&lt;/P&gt;
&lt;P&gt;For example, in other platforms we use mechanisms such as &lt;STRONG&gt;Spaces&lt;/STRONG&gt; in Kibana and &lt;STRONG&gt;Organizations&lt;/STRONG&gt; in Grafana to structure and manage dashboards at scale.&lt;/P&gt;
&lt;P&gt;Are there any official guidelines, best practices, or community recommendations regarding:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Dashboard naming conventions&lt;/LI&gt;
&lt;LI&gt;Foldering or organizational strategies&lt;/LI&gt;
&lt;LI&gt;Access control and permissions regarding create and read dashboards.&lt;/LI&gt;
&lt;LI&gt;Ownership and accountability&lt;/LI&gt;
&lt;LI&gt;Dashboard lifecycle management (creation, review, deprecation, retirement)&lt;/LI&gt;
&lt;LI&gt;Governance models for large-scale dashboard environments&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Any documentation, experiences, or recommendations from other Dynatrace users would be greatly appreciated.&lt;/P&gt;
&lt;P&gt;Thank you very much for your support.&lt;/P&gt;
&lt;P&gt;Best regards.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Sep 2026 05:50:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Best-practices-and-ways-to-organize-dashboards/m-p/304433#M5895</guid>
      <dc:creator>FranciscoMPalos</dc:creator>
      <dc:date>2026-09-17T05:50:02Z</dc:date>
    </item>
  </channel>
</rss>

