Blog Post

Microsoft SharePoint Blog
2 MIN READ

Enhance user interaction with the new Dashboard web part in SharePoint

VesaJuvonen's avatar
VesaJuvonen
Icon for Microsoft rankMicrosoft
May 15, 2025

New web part for all SharePoint sites

The Dashboard web part enables the integration of cards into your SharePoint sites and pages. Cards offer a consistent and enriched user experience, enhancing engagement. Previously, the Dashboard web part was exclusive to Home Sites in SharePoint. It is now extended to be available in Teams and Communication Sites.

This functionality enables teams within an organization to create their own dashboards with the richness of cards. There are out-of-the-box cards available to kick start the dashboard which can further be enhanced with any custom cards based on the need. Dashboard web part supports all custom card types created either using Card Designer or SharePoint Framework.

The authors can select the Manage Dashboard option leads to the create flow for the Dashboard which follows the Dashboard page where the author can add cards as show below.

Authors can choose pre-built cards and configure them for their teams or add custom cards available at the tenant level. They can also use Card Designer or custom cards which have been deployed to be available through the SharePoint app catalog. This dashboard can be added to any site page on particular site for user access.

 

With the dashboard web part, you can build combine web parts and cards to enhance the end user experiences in the sites. Here's few example designs on using this web part in SharePoint sites.

 

 

The features and capabilities mentioned in this blog post are demonstrated in the following video with Pooja Gulati (Microsoft), Sri Sai Mohan Suri (Microsoft) and Vesa Juvonen (Microsoft).

Frequently asked questions

When will this happen?

The feature is rolling out to Targeted Release customers and will continue to roll out to all customers through the end of May 2025

This message is associated with Microsoft Roadmap ID 486832.

Are all card types supported?

Yes. All cards from Microsoft and custom card types are supported. This includes also Card Designer cards and custom cards build with SharePoint Framework. There are no update requirements on the existing cards to enable them to be available in the dashboard web part. Any custom card which has been deployed globally from SharePoint app catalog, is available for the dashboard creation.

What do you need to prepare?

New web part will be available automatically as the feature starts rolling to worldwide across tenants. We will be publishing additional documentation and guidance on this also soon.

What is next?

We continue investing in these areas based on the customer feedback. Please continue providing us input and feedback on the already released features and on what you'd like to see us provide in future. 

 

Thanks for reading and letting us know any feedback or questions in the comments.

Updated May 15, 2025
Version 1.0

10 Comments

  • grant_jenkins's avatar
    grant_jenkins
    Steel Contributor

    VesaJuvonen​VesaJuvonen​/ PoojaG​  Another follow up on this. Can you let us know if this can be disabled in our tenant prior to rollout? This is urgent/critical for us and getting closer to rollout in our production tenant - we have 65k users that will be affected by this.

    Microsoft always say they want and value customer feedback, then get zero response when we post it. Note that I've tried multiple channels with Microsoft to get a response on this but unfortunately, we are still not getting anywhere.

    Feel free to reach out to me via private chat if that helps.

  • LucianoFaria's avatar
    LucianoFaria
    Copper Contributor

    I had the opportunity to test it, but I'm not able to create it in subsites. When I create the panel, it generates the file in the main site, and I can't link the panel to the subsite. I tried going to the created file and granting access to all subsite visitors, but the panel file still doesn't appear in the subsite.

    The panel already exists but is not loaded in the subsite.

    On the parent site, however, the panel loads perfectly.

     

    • Westronman2025's avatar
      Westronman2025
      Copper Contributor

      Why are you using subsites? The modern IA for SharePoint is hubs and associated sites. Subsites are now a legacy/deprecated technology.

    • grant_jenkins's avatar
      grant_jenkins
      Steel Contributor

      I think Microsoft should hide the dashboard webpart when you are on a subsite if it doesn't work. Subsites are part of the same Site collection, so good pick up that it doesn't work here. Not sure if they will add the ability to add on subsites in future, but if not, then the webpart should be hidden.

      • janko_schoettl's avatar
        janko_schoettl
        Copper Contributor

        grant_jenkins​ 

        The concept of subsites is an old approach and subsites should not be used anymore. Better to use Site Collections instead of subsites.

    • janko_schoettl's avatar
      janko_schoettl
      Copper Contributor

      hi LucianoFaria​ 

      This functionality does only work per site collection. You cannot show a dashboard of an site collection in another site collection (sub site).

  • LucianoFaria's avatar
    LucianoFaria
    Copper Contributor

    I had the opportunity to test it, but I'm not able to create it in subsites. When I create the panel, it generates the file in the main site, and I can't link the panel to the subsite. I tried going to the created file and granting access to all subsite visitors, but the panel file still doesn't appear in the subsite.

    The panel already exists but is not loaded in the subsite.

    On the parent site, however, the panel loads perfectly.

     

  • janko_schoettl's avatar
    janko_schoettl
    Copper Contributor

    I got the chance to test it a little bit today:

    • The functionality has a lot of potential and and the ideas will for sure come and are already there and to use a dashboard in every site would broaden the reach of adaptive cards also.
    •  Permissions
      • It seems every Site member (edit permission level) can access the dashboard, what is a little confusing, if you have a lot of editors in a site collection, they would destroy each others dashboard 🤔
      • It would be better to bind the Manage Dashboard link to the "design permission level", as I know many organizations which do not use  the real Owner group (full permission) anymore or they use a own provisioning tool where they do not assign "full permission" to site owners
    • Default Adaptive cards
      • The proposed cards have their purpose but in large organizations people would like to curate the cards proposed to the editor, as some organizations are still not yet ready to user things like Power Apps Card or Dynamics Cards, so a gradually introduction of cards would be suitable in respect to the maturity aspect.

    For sure we will see it grow.

  • grant_jenkins's avatar
    grant_jenkins
    Steel Contributor

    Hi VesaJuvonen​ /PoojaG​ . Providing some hopefully useful feedback.

    Firstly, it looks great, and I can see you've put a massive amount of work into this. I'm sure it will be a nice addition for many of your customers. However, we are not ready for this now. Questions/notes below:

    • Will there be an option for us to disable this across our tenant until we are ready to enable it? Please say yes (we're still desperately working on getting Site branding disabled as it goes completely against our brand strategy).
    • If just using the out-of-the-box Cards, there is not a lot of functionality we can get within the Card itself unless we extend them with SPFx. However, our company isn't using any SPFx and isn't set up for it (governance, development, support, etc.). Also, if we were going to use SPFx then we'd create Webparts instead of Adaptive Cards as we get full design and extensibility (Adaptive Cards by nature are structure and content only - no - or limited - design aspects).
    • Users will also start to use the Adaptive Cards Designer to generate their JSON they need to add back into the Cards. We don't have support in place to manage this aspect either when the Cards don't work as expected, or users ask for help designing them.
    • After creating a Site dashboard, are you able to delete it? I see that you can turn it on/off which might be ok instead of deletion.
    • For users to start using the dynamic connections (Graph/SP REST) do we need to enable this at the tenant level, or can it be site by site (hoping the later). If only tenant wide setting, then that's an issue for us.
    • SP REST API is limited to the current site which severely limits its usefulness. A lot of the data we would look to retrieve would potentially live on other sites. I know we can use the Graph connector, but limited data is available (think Site/Web properties, etc.). Is there anything on the roadmap to allow SP REST API to go across other sites?
    • Who can create and manage dashboards - only owners, or anyone with Edit rights?
    • Who can add the dashboard webpart to the site?
    • Who can create Cards? If it's only owners and they want people to create Cards for them, they will have to make those users owners, which is a governance/security concern (access to everything). Will there be a new role available for this, or how will it work?
    • I saw you had max number of Cards displayed = 5 (quite limited) - any reason for just that many?
    • When will it be in GA (or released as part of TAP)? You mentioned in the video it would be completed by the end of May, but the Microsoft Roadmap still says In Development?
    • Approvals: Most of our approvals are within custom Power Platform environments (not the default one) so none of those approvals show up as they have their own Dataverse environment and associated Approvals tables. Anything on the roadmap to fix this in general where we can have a global view of all approvals across all Power Platform environments?

     

    For Viva Connections (in relation to the Dashboard) in Microsoft Teams:

    • Can you allow us to remove the Viva Connections Footer that has links to your Viva Microsoft Site and the other Viva features? It seems a bit strange that we're forced to keep this as our footer.
    • Can you allow us to remove the dropdown showing the other Viva features? We don't want our users going directly to Viva Learning as we have a dedicated Learning site they should be directed to.
    • The Welcome [name] is always black text. I added a background image that was quite dark, and I almost couldn't read the Welcome message. It would be nice if it picked up the contrast of the image and rendered appropriately (light/dark).
    • The Navigation allows you to select links from the Global Navigation but doesn't retain any of the hierarchy that we have in our Global Navigation. It would be nice to somehow replicate this within the Microsoft Teams view. I'm not sure if it has any sort of syncing either - if we select a link from our Global Navigation then we update the Global Navigation, will that change reflect in Microsoft Teams?

     

    Sorry for the long feedback - hopefully, it helps you (Microsoft) and your customers when looking at these features.