Hi ,
Welcome to the Support Portal. How can we help?

Troubleshooting SharePoint

Table of Contents



Sometimes we receive questions that users cannot see certain sites and/or libraries within the Workspace. This guide will explain you how the Workspace tries to read out the SharePoint permissions and how to troubleshoot. If you're still facing issues after reading this article, please contact support.


How does Workspace read the permissions?

You can set permissions in SharePoint two ways. 

  • Permissions per site/branch of the SharePoint hierarchy (common via regular permission structure).
  • Directly add permissions to a document library, folder and/or files (common via sharing).


Back to top


Permissions per site/branch of the SharePoint hierarchy

When you assign permissions to SharePoint sites, you usually have read permissions on the whole path of the hierarchy of that specific site. This way you can browse through the hierarchy within SharePoint and navigate to other sites/document libraries. 

Back to top


Directly add permissions to a document library, folder and/or files

Commonly when you share documents and/or files, you grant permissions to that specific document library, folder and/or file and its children. Within SharePoint you can easily access the files, but not the complete path. 

Back to top


Difference Workspace vs SharePoint

Within the Workspace we search all site collections and sites for the signed in user. We do that via the following search query;

"STS_Site" AND webtemplate<>"SPSPERS"

To search for a specific site, use the following search query;

contentclass:STS_Site Path:{SiteCollection.URL}*

It can occur that the site is not available within the Workspace but in SharePoint. Please check the following;

  • Open the root SharePoint site and search for the following command;
    "STS_Site" AND webtemplate<>"SPSPERS"


  • When the site is not listed, it's not being indexed by the SharePoint Search. Therefore, there is no possible way for us to list the site. Please re-index the site manually or wait for it to be indexed automatically.
  • If it is listed, please make sure the user has all the permissions for the SharePoint site.

The permissions are built differently than in SharePoint. If we need to list the whole path to a document/library, you need at least read permissions on the parent items to show the whole path within the Workspace.

You can share a Workspace link directly if someone has unique permissions to that specific item. But they will never be able to browse to the item themselves. 
If you have shared the folder/files with the user, they will be able to see the shared folder/files within My Documents -> Shared with me
Make sure the user has the permissions from top to bottom, so from the Root URL to the Document library. Workspace needs the user to have read permissions to the whole path.



Sites names not up to date or missing in Workspace

If sites are missing, you can use the Microsoft Graph API and the SharePoint search query to check which sites are available to you as an admin or a specific user (in some cases disabling faster loading experience (preview) can solve this issue).

When a user is added to a SharePoint group, the user is added to the corresponding SharePoint site. It doesn't take long for Workspace to detect these changes and sites are visible in Workspace within (give or take) 20 minutes. However, adding users to Teams sites takes much longer (this is based on Microsoft 365 groups). You may have to wait 24 hours for Workspace to detect the site.

Site name not up to date? Example: there was a change in naming of document libraries and the new names are not up to date in the Graph Explorer, the Workspace will not be updated with the new names from the document libraries either. 

Back to top