SharePoint connector · Coming soon

Coming soon: Your contracts stay where they are.

Planned: Treasure reads SharePoint, OneDrive and Teams in place — no migration, no new archive.

Coming soon: The SharePoint connector is in preparation and not yet available. This page describes the planned scope. Enquire now to be put on the pilot list. Today you import contracts into Treasure via folder upload or drag & drop; search, classification, contract data and AI review are then available in Treasure.

Many existing contracts sit in SharePoint, OneDrive and Teams without their content being analysed. With the planned connector, Treasure Contracts is to open up this inventory in place: searchable, classified, with terms and termination provisions extracted — without moving files and keeping your Microsoft permissions.

Enquire now See the planned process

Building blocks of the M365 connection

In place

Files remain
in Microsoft 365

Rights

Permissions
continue to use

Answer with
Source reference

Contract data

Terms and
termination provisions

Three functions

What the connector is designed to do

Planned scope — for contract management and legal alike.

In-place indexing

Planned: Treasure indexes SharePoint, OneDrive and Teams contracts directly in your tenant. The files remain unchanged and permissions are retained.

Natural language search

Available in Treasure today: search and chat across uploaded contracts, with answers citing the source passage verbatim. Planned: the same search across your SharePoint inventory, with a link to the original.

Terms & termination provisions

Treasure extracts terms and termination provisions as contract data; they can be filtered and exported. Automatic reminders before deadlines: coming soon.

Planned onboarding path

From Microsoft tenant to searchable inventory

Planned: Treasure connects, indexes and hands over the inventory step by step — without moving documents to a new repository.

Tenant connection

Microsoft Graph API

Indexing

in place

Classification & enrichment

structured

Handover

productive

Step 1 · Step 1 of 4

Tenant connection

Treasure connects to your M365 tenant via Microsoft Graph API. Authentication via Azure AD (Entra ID), scope of authorization can be selected granularly - your IT remains in control.

Setup

Step 2 · Step 2 of 4

Indexing

Treasure scans SharePoint libraries and Teams channels, identifies contracts and extracts clauses. The files remain unchanged where they are.

Index

Step 3 · Step 3 of 4

Classification & enrichment

Contract type, contractual partner, term and values are automatically recognized and stored in the treasure index. Existing metadata is adopted, not overwritten.

Classify

Step 4 · Step 4 of 4

Handover

You search the portfolio, export contract data and start AI reviews in Treasure.

Go live

Features in detail

Contract intelligence in the Microsoft tools your team already uses

What is available today and what is planned as “coming soon”.

Searchable document management with filters in Treasure Contracts

Permissions

Adopt Microsoft permissions (planned)

Coming soon: permissions from SharePoint are to be adopted so you do not maintain access twice. Today you control access through the role and permission model in Treasure.

Coming soon: Treasure bot in Teams

Coming soon · Teams integration

Treasure bot in Teams

Planned: ask questions directly from Teams — the answer arrives in the chat, with a source reference and a link to the original.

Treasure Contracts Word add-in with contract review and redline suggestion

Word add-in (first version)

Review findings directly in Word

After the playbook review in Treasure, you open the contract in Word: view findings with traffic-light rating, jump to the source passage, insert a suggestion as a tracked change and save the edited version as a new version in Treasure. Starting a review from Word: coming soon.

Coming soon: Power Automate

Coming soon · Power Automate

Trigger via Power Automate

Planned: contract events are to trigger Power Automate flows, such as an email to the owner or an entry in third-party systems. Available today: notifications via email and Slack, and API keys.

Classic CLM vs. Treasure-in-Place (planned)

Why the connector is designed to work without migration.

Two paths to a searchable contract portfolio. General classification; varies by vendor.

Classic CLM/DMS

With Treasure Contracts

Contracts migrate

Migration to the CLM repository

Effort depends on the inventory

Contracts migrate

Stay in SharePoint/OneDrive

Treasure indexes in place (coming soon)

Permissions

Separate permissions in the CLM

Maintained separately

Permissions

Adopt Microsoft permissions

Coming soon

Word workflow

Export → CLM → Import

Three steps, several versions

Word workflow

Word add-in (first version)

Findings and suggestions in Word

Only what was migrated

Non-migrated inventory is missing

M365 inventory searchable (coming soon)

Today: contracts imported via folder upload

Deadlines

Often manually maintained lists

Dependent on individuals

Deadlines

Extracted from the contracts

Reminders: coming soon

SharePoint + Treasure

SharePoint connector: enquire now to join the pilot list.

The connector is in preparation. Until then, we show you on your own contracts how search and review work in Treasure — imported via folder upload. 4 weeks unconditional right of withdrawal with full refund.

EU hosting · GDPR · designed for the requirements of § 43e BRAO and § 203 StGB (our own assessment)

Enquire now Security & GDPR in detail

FAQ

Frequently asked questions

We already have a DMS or use SharePoint as contract storage - why Treasure?

Many repositories store contracts without analysing them. Treasure does not replace SharePoint; it adds classification, search, extracted contract data and AI review. Today you import the inventory via folder upload; the direct SharePoint connector is coming soon.

Do we need to move or duplicate documents?

Not with the planned connector: Treasure is to index your contracts in place via the Microsoft Graph API, and the files remain in SharePoint, OneDrive and Teams. Until then, you upload contracts to Treasure via folder upload or drag & drop.

How secure is the connection - keyword GDPR and professional secrecy?

The connector is planned to run via Microsoft Entra ID with granularly selectable permissions. Treasure processes data in EU data centres (AWS Frankfurt; AI via EU regions of AWS, Google and Microsoft). The provider is the German company boutiq ai GmbH. No training on your data, ISO 27001 certified information security, designed for the requirements of § 43e BRAO and § 203 StGB (our own assessment). AI reviews are recorded in the audit trail.

What happens to new contracts after onboarding?

Planned: Treasure detects new or changed contracts in the connected libraries and classifies them. Today, new contracts reach Treasure via upload or the email inbox and are classified automatically.

Free · PDF workbook · 12 chapters

CLM implementation with AI — From A to Z

The complete workbook for your CLM project: over 15 ready-made prompts, checklists and templates from requirements analysis to rollout and ROI.

Double opt-in, unsubscribe anytime with one click. No spam.

Get it free View all freebies →