Browse and connect

Plan SharePoint capture and export for your Mind

SharePoint capture brings documents from an approved library or folder into your Mind. Export moves selected information in the other direction. These jobs need different permissions and connections. This page helps an owner define the scope and check availability before arranging either job.

Contents

Check whether the package is offered

The product source includes SharePoint Sensor and SharePoint Mirror packages. They were not entries in the selected customer catalog used for these guides. Their presence in source or a published app artifact does not make them installable in every Mind.

Check your Mind’s store with its authorised installer. If the intended package is absent, ask Mensara whether there is a supported setup for your version and Microsoft environment. Do not substitute another sensor or create a general Microsoft connection and assume the package will start. The catalog separates currently selected extensions from this availability-qualified route.

Scope a read-side capture

For a supported SharePoint Sensor setup, identify the tenant, library, approved folders and destination area. Decide whose documents can be read and who may read the resulting captures. The sensor polls approved folders and can create model-generated document cards, so it needs the appropriate service connection, model route, budget and review policy.

Give the installer one harmless document to use as an acceptance check. After a normal scheduled run, inspect its source link, extracted text, card and destination. A generated description is not a substitute for the underlying document. Keep a route back to it.

Scope a write-side export

SharePoint Mirror is a separate package for exporting one approved Mind zone as Markdown into a dedicated library folder. It requires write-side access to that destination. Agree which area may leave the Mind, which folder receives it and who can read that folder before granting the connection.

Use an empty, dedicated test destination first. Have the owner inspect the exported files and confirm that excluded areas are absent. A successful export says files were written; it does not make the SharePoint copy a complete backup with recovery keys and history.

Keep permissions and recovery explicit

Microsoft permissions, the app’s connection grant and access to saved Mind records are separate controls. Removing one does not prove the others have disappeared. Check each relevant system after a scope change.

If a supported installation cannot read the sample or produce its expected output, retain its version, run reference and bounded error for the installer. Do not broaden the tenant grant to diagnose an unrelated failure. Use the capture checks and model settings to locate the missing prerequisite.

Related

Choose an app, sensor or connector for your Mind · Review records imported from business tools · Back up, recover and export your Mind · Choose access for a teammate

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://app.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://app.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Plan SharePoint capture and export for your Mind

Apps, sensors and connectors · Browse and connect · [How it works](https://app.mensara.ai/how-it-works)

SharePoint capture brings documents from an approved library or folder into your Mind. Export moves selected information in the other direction. These jobs need different permissions and connections. This page helps an owner define the scope and check availability before arranging either job.

[Page as Markdown](https://app.mensara.ai/how-it-works/sharepoint.md)

## Check whether the package is offered

The product source includes **SharePoint Sensor** and **SharePoint Mirror** packages. They were not entries in the selected customer catalog used for these guides. Their presence in source or a published app artifact does not make them installable in every Mind.

Check your Mind’s store with its authorised installer. If the intended package is absent, ask Mensara whether there is a supported setup for your version and Microsoft environment. Do not substitute another sensor or create a general Microsoft connection and assume the package will start. [The catalog](https://app.mensara.ai/how-it-works/apps-sensors-connectors) separates currently selected extensions from this availability-qualified route.

## Scope a read-side capture

For a supported SharePoint Sensor setup, identify the tenant, library, approved folders and destination area. Decide whose documents can be read and who may read the resulting captures. The sensor polls approved folders and can create model-generated document cards, so it needs the appropriate service connection, model route, budget and review policy.

Give the installer one harmless document to use as an acceptance check. After a normal scheduled run, inspect its source link, extracted text, card and destination. A generated description is not a substitute for the underlying document. Keep a route back to it.

## Scope a write-side export

SharePoint Mirror is a separate package for exporting one approved Mind zone as Markdown into a dedicated library folder. It requires write-side access to that destination. Agree which area may leave the Mind, which folder receives it and who can read that folder before granting the connection.

Use an empty, dedicated test destination first. Have the owner inspect the exported files and confirm that excluded areas are absent. A successful export says files were written; it does not make the SharePoint copy a complete backup with recovery keys and history.

## Keep permissions and recovery explicit

Microsoft permissions, the app’s connection grant and access to saved Mind records are separate controls. Removing one does not prove the others have disappeared. Check each relevant system after a scope change.

If a supported installation cannot read the sample or produce its expected output, retain its version, run reference and bounded error for the installer. Do not broaden the tenant grant to diagnose an unrelated failure. Use [the capture checks](https://app.mensara.ai/how-it-works/connections-and-capture#check-a-harmless-first-capture) and [model settings](https://app.mensara.ai/how-it-works/model-connections) to locate the missing prerequisite.

## Related

- [Choose an app, sensor or connector for your Mind](https://app.mensara.ai/how-it-works/apps-sensors-connectors)
- [Review records imported from business tools](https://app.mensara.ai/how-it-works/imported-records)
- [Back up, recover and export your Mind](https://app.mensara.ai/how-it-works/backup-restore-ownership)
- [Choose access for a teammate](https://app.mensara.ai/how-it-works/right-access)

Previous page: [Capture Telegram chats in your Mind](https://app.mensara.ai/how-it-works/connect-telegram)

Next page: [Review records imported from business tools](https://app.mensara.ai/how-it-works/imported-records)

An imported record is information copied or interpreted from another system, such as a customer note or contact update.

[Join the waitlist](https://app.mensara.ai/#waitlist)