> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/release-notes/february-2026/sharepoint-updates.md).

# SharePoint Updates

### Introduction

This release introduces enhanced SharePoint File Selection capabilities in Unifize.

Organizations can now configure a specific SharePoint folder path within Process Builder and allow users to browse and select files directly from that configured folder when attaching files in checklist fields.

This improves file governance, folder-level control, and structured document access within workflows.

File selection is now restricted to the configured SharePoint folder path defined at the process level, ensuring consistency, compliance, and controlled document usage across records.

### Release Capabilities

#### 1. Configured Folder-Based File Selection

a. Admins can configure a SharePoint folder path within Process Builder settings.\
b. The configured folder acts as the source directory for file selection.\
c. Users can browse files and subfolders within the configured path.\
d. File picker displays only contents from the defined folder location.

#### 2. Direct File Attachment from SharePoint

a. Users can select “Add from SharePoint” from the attachment menu.\
b. A SharePoint file picker modal opens within Unifize.\
c. Selected files are attached directly to the checklist file upload field.\
d. Attached files are visible in both the checklist field and conversation attachment area.

#### 3. Folder Navigation & Multi-File Selection

a. Users can navigate across subfolders within the configured folder path.\
b. Multiple files can be selected and attached in a single action (if enabled).\
c. The picker reflects the latest folder contents (additions/removals).\
d. Empty folder states are handled with a clear “No files available” message.

#### 4. Permission-Aware File Access

a. The file picker respects SharePoint folder-level permissions.\
b. Users without folder access receive a permission/access error.\
c. If Microsoft authentication is missing or expired, users are prompted to log in.\
d. Guest users can access files based on their SharePoint tenant permissions.

#### 5. File Integrity After Rename or Move (Within Same Site)

a. Renaming a SharePoint file does not break edit, view, or download functionality in Unifize.\
b. Moving a file within the same SharePoint site does not break access.\
c. File references remain stable within the configured folder structure.

#### 6. Controlled Behavior Across SharePoint Sites

a. If a file is moved across SharePoint sites, edit/view/download from Unifize will fail (expected behavior).\
b. This prevents unintended cross-site access drift.\
c. Users receive an appropriate access/error response.<br>

### Supported Environment

* Web App (Chrome supported)
* Not supported in Mobile App
* Not supported in PWA
* Not supported in Gov Cloud

### Before vs After

| Before                                                                             | After                                                                                           |
| ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
| Users could attach SharePoint files but folder-level browsing control was limited. | File selection is restricted to a configured SharePoint folder path defined in Process Builder. |
| Folder navigation experience was less structured.                                  | Dedicated SharePoint picker with folder navigation and multi-file support.                      |
| Access handling depended on session state and implicit behavior.                   | Authentication prompts, permission validation, and guest access support are enforced.           |
| Rename/move behavior required validation improvements.                             | Rename and same-site move operations maintain stable edit/view/download functionality.          |

\
\ <br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.unifize.com/release-notes/february-2026/sharepoint-updates.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.