Skip to main content
Rather than asking you to paste excerpts into a chat window, Parlé gives the agent direct access to the documents stored in the project. When you ask a question that requires reading a contract, scanning a balance sheet, or summarizing a presentation, the agent reaches into the project’s file store and runs a tool call against it. You get an answer grounded in the actual source material — not one built from text you copied in manually.

​
The four file tools

Whatever storage a project is rooted at — Parlé Cloud Storage, a SharePoint document library, or a Google Shared Drive — the agent sees the same four normalized operations. Nothing in a conversation depends on which provider is behind them.
File tools are not read-only. The agent can create, overwrite, and delete files in the location the project is rooted at. That is deliberate — it is how a drafted deliverable ends up in your SharePoint folder rather than trapped in a chat window — but it means the grant you give Parlé on that location is the real control. If you want read-only behavior, grant read-only access on the provider’s side: see Storage.
Deletions go to your SharePoint recycle bin or Drive trash when the project is rooted in your own tenant, so your normal retention and recovery rules apply.

​
Supported file types

Scanned PDFs that contain only images cannot be read. A photographed or scanned document is an image as far as the file is concerned, and no text can be extracted from it. Use a PDF that has a text layer, or run the document through OCR first.

​
Adding files to a project

1

Open the project's Files tab

Navigate to the project and select Files.
2

Add your documents

Upload them here, or — if the project is rooted in SharePoint or Google Drive — simply put them in that folder the way your team normally does. Files your team adds at source are visible to the agent’s tools without any upload step in Parlé.
3

Confirm the agent can see them

Start a conversation in the project and ask the agent to list the files, or ask a question that references a document by name.

​
Where file tools are available

File tools work in project conversations only. A personal conversation has no project, so it gets neither file tools nor integrations.

​
Grounded answers

Because the agent works by calling file tools — not by consuming a blob of pasted text — an answer it gives can be traced back to a specific source document, and the tool calls it made are recorded in your organization’s audit log against the user and the conversation. The log records that a file was read or written, not the file’s contents. This traceability matters in professional services contexts where the answer is only as good as the source. When you take an AI-assisted conclusion into a client deliverable or a legal brief, you need to be able to point to exactly where it came from.
After the agent gives you an answer based on a file, ask it to quote the exact text it drew from: “Show me the verbatim language from the contract that supports that conclusion.” This gives you a defensible reference you can drop directly into a memo or client communication.

​
Finding a passage by meaning, not just by name

Listing and reading files gets you to a document you already know the name of. To find a passage by what it says rather than its exact wording, see Semantic File Search — the agent’s fs_semantic_search tool, and the org-level switch that controls it.

​
Firm-wide documents are a different thing

File tools reach this project’s files. Documents that are true for your whole firm — the expenses policy, the staff handbook, the delivery methodology — belong in organization knowledge instead, where they are indexed once and can be quoted with a citation in every conversation across the organization.