> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/troubleshooting/causes-of-missing-content/some-sites-or-libraries-do-not-appear-in-konnekt.md).

# Some sites or libraries do not appear in KONNEKT

## Problem

SharePoint Online sites or libraries which should be mapped via auto mapping do not appear in KONNEKT.

## Background

KONNEKT runs a search on SharePoint Online to discover sites & libraries. To find libraries here, the user must be a member of the site.

In some cases, users may be owners of a site, but not members. This results in not discovered sites or libraries.

{% hint style="info" %}
If a Site Collcetions are marked as**"restricted"** with [Restricted Content Discovery (RCD)](https://learn.microsoft.com/en-us/sharepoint/restricted-content-discovery) their content is less discoverable in tenant-wide search.
{% endhint %}

## Solution

Ensure, that owners of sites are also members. See [here](https://docs.microsoft.com/en-us/sharepoint/troubleshoot/search/search-results-dont-appear-for-group-owners) for more details.

### Similar Problems

Please also check this page: [Sites missing or folders empty](/troubleshooting/causes-of-missing-content/sites-missing-or-folders-empty.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konnekt.io/troubleshooting/causes-of-missing-content/some-sites-or-libraries-do-not-appear-in-konnekt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.