Skip to main content
When a lawyer uploads a due diligence document or an accountant attaches a client’s financials to a project, that file should not travel to a third-party storage environment your firm has no control over. Most cloud AI tools persist uploaded documents in their own infrastructure — which creates data residency concerns, potential conflicts with client confidentiality agreements, and murky answers on security questionnaires. Parlé’s native storage integration addresses this: on the Business plan and above, a project can be rooted directly in a SharePoint document library or a Google Shared Drive inside your own tenant, governed by your existing permissions and retention policies.
Native storage integration is available on the Business plan and above. Otherwise, projects use Parlé Cloud Storage — managed storage scoped to your organization, which needs no setup.

​
Least-privilege by design

Parlé reaches your files using its own application identity, scoped to only the specific locations you grant — never your whole tenant. This is the part that matters on a security questionnaire, so it is worth being precise about:
  • Parlé does not provision anything in your tenant. You choose an existing site, library, or Shared Drive; Parlé is granted access to it.
  • Each location is granted explicitly, one at a time. Granting one SharePoint site does not grant another. A private or shared Teams channel is its own SharePoint site and needs its own grant.
  • The agent works when nobody is online. Because access is held by an application identity rather than a signed-in user’s session, a long-running task does not depend on someone keeping a browser tab open.
  • Deletions land in your recycle bin. Files deleted through Parlé go to the SharePoint recycle bin or Drive trash, where your normal retention and recovery rules apply.
The agent can write, not just read. Project file tools cover listing, reading, writing, and deleting files in the location the project is rooted at. Grant the permission level you actually want: SharePoint sites can be granted read-only, and a Google Shared Drive can add Parlé as Viewer rather than Content manager.

​
Connecting a location

Storage is set up in two stages: an Org Admin enables the provider once for the organization, then each project is pointed at a specific library or drive.

SharePoint

Enable the SharePoint host for your org, grant Parlé access to each site, then root a project at a document library or folder. Includes Teams channel folders.

Google Drive

Add Parlé’s service account to each Shared Drive as Viewer or Content manager, then root a project at that drive.
Parlé verifies it can actually list the location before saving the configuration, so a permissions gap surfaces at setup rather than mid-conversation.

​
Permissions and access

Storage access in Parlé is project-scoped, not per-user. This is an important distinction to get right when deciding where to link a project to:
  • A project is rooted at one location. Everyone who can open that project can use the agent’s file tools against it.
  • Who can open the project is controlled in Parlé by the project’s visibility and member list (see Roles & Permissions).
  • Parlé’s own grant on the site or Shared Drive is what bounds the blast radius on your side. It reaches that location and nothing else in your tenant.
Parlé does not mirror individual users’ SharePoint or Drive permissions into a project. If a document library contains material that only some project members should see, root the project somewhere narrower rather than relying on per-file permissions to filter it.
Because files live in your SharePoint or Google Drive, your existing data loss prevention (DLP) policies, retention labels, and eDiscovery tooling apply to Parlé project files automatically — no additional configuration needed.

​
When a location moves or disappears

Parlé binds to the folder itself, not to its name. Renaming a SharePoint folder or a Teams channel does not break the project. Deleting the folder does. The project’s Storage settings will show “needs reconnecting”, and an admin re-picks a folder to fix it. Parlé deliberately will not fall back to another folder that happens to have the old name, because a new folder reusing that name could belong to a different client.
Disconnecting storage does not delete your files. Everything remains in your SharePoint site or Shared Drive exactly as it was.