Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

Is your feature request related to a problem?

Description:
Currently, the SharePoint connector in RAGFlow works by accepting a Site URL, and all folders under that site are considered for document retrieval. However, there is no option to configure or restrict the connector to a specific folder within the site.

This limitation makes it difficult to control the scope of document retrieval when the SharePoint site contains multiple folders with unrelated or sensitive content. As a result, all documents across the site are processed, which can impact both performance and relevance.

Describe the feature you'd like

Current Behavior:

• User provides a SharePoint Site URL
• All folders and documents under the site are automatically included
• No option to filter or restrict to specific folders

Expected Behavior:

• Ability to configure one or more specific folders within the SharePoint Site
• Only documents from the selected folder(s) should be considered for indexing and retrieval

Proposed Solution:
Introduce a configuration option in the SharePoint connector to:

• Select a specific folder path (e.g., /Shared Documents/ProjectA)
• Optionally include/exclude subfolders
• Support selection of multiple folders

Benefits:

• Improved relevance of retrieved content
• Better performance by limiting the dataset
• Enhanced control over document access
• More targeted and efficient use-case implementation

Use Case Example:
A user wants to retrieve documents only from /Shared Documents/ProjectA instead of scanning the entire SharePoint site, which contains multiple unrelated folders.

Conclusion:
Adding folder-level configuration will significantly improve usability, efficiency, and precision of the SharePoint connector in RAGFlow.

Describe implementation you've considered

No response

Documentation, adoption, use case

Additional information

No response