A module within Microsoft Viva that serves as an enterprise social networking platform. It fosters community building, open dialogue, and knowledge sharing across an organization.
Hi Emma,
On your Pinned-section workaround, any community member can add or delete a pinned resource, and the link then sits at the bottom of the Pinned section on the community's home page. That's a community-level feature, not per-user, so once it's pinned it should render for every member who can load the community page, this isn't something you set individually per person.
A pinned tile is just a shortcut, it doesn't grant access to what it points to. If your user can see the tile but clicking it fails or shows "Access Denied," they likely isn't a member of the Microsoft 365 Group / SharePoint site backing that document library, even if they're a Viva Engage community member. You have to verify their permissions directly on the SharePoint site (Site permissions > Members) for this workaround.
According to MC1384422, Microsoft is mid-rollout on a redesign of Viva Engage's navigation and right-side panel, running from late June 2026 through an expected completion in mid-August 2026. As part of it, the "Community resources" module, the one that auto-surfaced a community's linked SharePoint library and site, is being removed from the right-side panel, along with an old Q&A importer module. However, that functionality isn't gone, it's now reachable through the overflow menu inside the Files tab rather than sitting on the panel automatically. So the automatic SharePoint surfacing is removed, not the Files tab itself.
Note: This link is shared by community members for your convenience. It points to a third-party site that is not managed or verified by Microsoft. We can’t guarantee the quality, safety, or suitability of any content or software found there. Please review carefully and make sure you understand any potential risks before using it.
Since this is a staggered rollout still in progress today, it's worth considering raise a support ticket raise a support ticket with Microsoft Support through the Microsoft 365 Admin Center for deeper investigation. They have access to backend configurations and can perform a more in-depth investigation. At the very least, they can provide the most effective workaround to ensure your experience remains smooth and secure.
I hope this helps move the case forward. Should you have any further questions or need additional assistance, please feel free to share them in the comment below. I'm very happy to help.