viva engage access to documents in a community

Hi Emma,

When a specific user is missing the top navigation line (or the Files tab) in a Viva Engage community while others see it fine, it usually points to a membership sync delay, licensing issue, or guest permission setting.

1. If the user is internal (same organization)

• Check membership status: Have the user open the community link directly. Ask them if they see a normal community view, or a "Join" / "Request Pending" prompt.
• Ensure the user has an active Viva Engage / Yammer core license assigned in the Microsoft 365 Admin Center.
• Ask the user to test in an InPrivate / Incognito window or perform a hard refresh (Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac).

2. If the user is an external guest

• Azure AD B2B guest status: Standard conversation guests in Viva Engage do not automatically get access to SharePoint-backed tabs. For an external guest to see and access Files, they must be added as an Azure AD (Entra ID) B2B Guest in your tenant first.
• SharePoint permissions: Even with B2B status, external guests typically need to be explicitly granted access to the underlying SharePoint document library to upload or edit files.

So as the first step, t’s worth confirming:

1. In the community's admin settings, double-check that the "Files tab" and "Community resources" toggles are set to On.
2. Confirm that the community is Microsoft 365 Connected (unconnected communities do not feature a native Files tab).

For more information, please consult

Viva Engage file storage overview | Microsoft Learn

Manage Viva Engage community resources | Microsoft Support

I hope these information provide some information and clarity to your issue. If you have any questions, please don't hesitate to reach out.

If the answer is helpful, please click 'Yes' and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

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.