Files: Google Drive, SharePoint and OneDrive, Amazon S3, Azure Storage, Google Cloud Storage
How to connect file stores so people can find files where they already are and read the text inside them. Files are read only when someone asks, never indexed. Everything is read-only, with one exception you choose: agents may save the files they make (a report, a spreadsheet) to a folder in Google Drive, SharePoint or OneDrive (see Saving files to a folder); a chat saves a file only after you click Apply on a preview.
Status: Google Drive is Verified: tested on a real Google account. SharePoint, OneDrive and Amazon S3 are Available: built on each service's published API, and validated in your environment during onboarding. Azure Data Lake and Blob Storage, and Google Cloud Storage, are Pilot: new or partial, built on each service's published API.
At a glance
| Connects through | Sign-in | Network | Status | First test question | |
|---|---|---|---|---|---|
| Google Drive | Google Drive API | Personal sign-in | Nothing to open | Verified | "Find files about the Corvanta renewal in my Google Drive." |
| SharePoint and OneDrive | Microsoft Graph | Personal sign-in | Nothing to open | Available | "Find SharePoint sites about sales", then "Find files about the Corvanta renewal." |
| Amazon S3 | Amazon S3 API | Shared account | Nothing to open | Available | "List the files at the top of s3:docs." |
| Azure Data Lake and Blob Storage | Azure Blob Storage REST API | Personal sign-in | Nothing to open, unless the account allows only selected networks | Pilot | "List the files in azure_storage:lake." |
| Google Cloud Storage | Cloud Storage JSON API | Personal sign-in | Nothing to open | Pilot | "List the files in gcs:docs." |
Add each source with the usual steps. The network answers are explained in What your network needs. If the first test question fails, the error message tells you what to fix: look it up under When something goes wrong below.
How it works
- Read on demand, never indexed. SourceLace does not crawl or index anyone's files. Every answer is read live from your systems, unless your organization has chosen Saved answers, an optional add-on your admin turns on system by system. When someone asks to read a file, SourceLace downloads that one file, reads its text, and returns it in chunks. The chunks are held like any other result (up to 30 minutes) and then forgotten.
- Finding files uses each store's own search: Google Drive's search, Microsoft Search for SharePoint and OneDrive, and file names for S3, Azure Storage and Google Cloud Storage. So Google Drive, SharePoint and OneDrive find files by their text as well as their names, while S3, Azure Storage and Google Cloud Storage find them by name, unless your admin chose to search inside their files too: see How S3, Azure Storage and Google Cloud Storage are searched.
- What it can read: PDF, Word (
.docx), Excel (.xlsx), PowerPoint (.pptx), CSV, plain text (and Markdown, JSON, HTML), and Google Docs, Sheets and Slides. Older.doc,.xlsand.pptfiles, images, and scanned PDFs without a text layer are not read; SourceLace says so instead of guessing. Password-protected PDFs cannot be read. - Limits: files up to 25 MB; up to 400,000 characters of text per file (longer files are marked
text_truncated); PDFs up to 1,000 pages; Office files that unpack to more than 250 MB are refused.
| Source | Kind | Who decides what someone can read |
|---|---|---|
| Google Drive | google_drive |
Each person signs in with their own Google account. Drive's own sharing applies. |
| SharePoint and OneDrive | microsoft_files |
Each person signs in with their own work or school account. SharePoint and OneDrive permissions apply. |
| Amazon S3 | s3 |
The source, not the person. See Amazon S3. |
| Azure Data Lake and Blob Storage | azure_storage |
Each person signs in with their own work account. Their Azure roles (such as Storage Blob Data Reader) and Data Lake access control lists apply. |
| Google Cloud Storage | gcs |
Each person signs in with their own Google account. Their Google Cloud IAM roles (such as Storage Object Viewer) apply. |
How people use it
Every file source takes one query language, files: a small JSON object with an action.
| Action | Example | What it does |
|---|---|---|
search |
{"action": "search", "text": "corvanta renewal"} |
Finds files with the store's own search. "match": "name" matches names only; the default "content" also matches text inside files where the store supports it (in S3, Azure Storage and Google Cloud Storage, where the admin chose names and file contents). A hit found by its text has a snippet showing where. Optional: "folder", "modified_after": "2026-09-01", "limit" (up to 200). |
list |
{"action": "list", "folder": "root"} |
The files and folders in one folder. root is My Drive, your OneDrive, or the top of the bucket or container. |
drives |
{"action": "drives"} |
Where files live: shared drives, SharePoint document libraries (add "text": "sales" to find sites by name), or the source's buckets and containers. |
read |
{"action": "read", "file": "<id>"} |
The file's text, in chunks of 4,000 characters ("chunk_chars" up to 20,000), 10 chunks at a time ("chunks" up to 50). "from_chunk": 10 reads further. |
get_record with object files and a file id returns the file's details and the first 20,000 characters of its text.
Searching everything. Google Drive, SharePoint and OneDrive sources are also searched by Searching everything, where it is on, together with your other systems, by name and by the text inside files. So are Amazon S3, Azure Storage and Google Cloud Storage sources whose admin chose Names and file contents, in the folders the admin allowed, and Search index sources. Sources searched by names only are not: ask them directly.
How S3, Azure Storage and Google Cloud Storage are searched
These stores cannot search inside files by themselves, and SourceLace never copies or indexes your files. So an admin chooses, for each source, how it is searched: How this source is searched on Connections (option search_contents).
| Choice | What a search does | Pick it when |
|---|---|---|
| Names only (the default) | Finds files by their names, anywhere in the source. Reading a file you name still gives its text. | Most buckets: people know roughly what a file is called or which folder it is in, or the bucket holds many large files. |
| Names and file contents | In the folders you allow, finds files by name and by the text inside them, with a short passage showing where the words are. The files are read when someone searches, and their text is forgotten straight after: nothing is copied or kept. | A few folders of documents people look for by what they say, such as contracts, policies or reports, small enough to read during a search. |
| Your own search index (a separate source) | Asks the search index your organization already runs over these files, such as OpenSearch, Elasticsearch or Azure AI Search, and links back to each file. | Large stores, or files people search all the time: your index answers over everything it holds. See Search index. |
With Names and file contents:
- Only the folders and file types you allow. Choose up to 20 folders whose files may be read (
content_folders, written bucket/folder/, inside the source's buckets and folder) and, if you like, the file types (content_types: PDF, Word, Excel, PowerPoint, CSV, text and HTML; all of them when you choose none). Files anywhere else are never read for a search. - Searches look in those folders. A search finds files there by name and by text. Choose one of the folders, or a folder inside one, to search a smaller part. To find a file by name anywhere in the source, ask for a names-only search (
"match": "name"). - Clear limits. One search reads at most 200 files and 50 MB, for at most 20 seconds. Your admin can lower these under Limits (Files one content search reads, Bytes one content search reads, Time for one content search). When a search stops at one of them, it says which, answers with what it found, and is marked incomplete: choose a smaller folder to search the rest.
- Files it cannot read are skipped, such as damaged or password-protected files and files over the largest file read, and the answer says how many.
- On the record. Each search is in your audit trail with how many files it read, never their text.
Finding files faster in S3, Azure Storage and Google Cloud Storage
Amazon S3, Azure Storage and Google Cloud Storage cannot search by themselves, so SourceLace finds files there by looking through their names, several folders at the same time. Three things make it faster:
- Search inside one folder. A search inside one folder looks through only that folder's names, so it is faster than a search of the whole source and finds more in a big bucket. Ask for it in plain words ("Find the Q3 plan in the reports/2026 folder of s3:docs"), or add
"folder"to a search. - Favourite folders. Folders your organization or you use most are searched first, listed first by
drives, and offered first wherever you choose a folder. An admin sets the organization's favourite folders on the source (optionfavourite_folderson Connections). Each person can keep up to 20 of their own: on My connections, press Favourite folders on the source, find a folder by typing the start of its name, and press Add. Only the folder paths are saved, never file names or contents, and only folders inside the source's buckets and folder can be chosen. Your own favourites are yours alone. - A clear limit. One search looks through at most 10,000 file names (your admin can lower it under Limits, as File names one search looks through). When a search stops there, the answer is marked incomplete and says: "Searched the first 10,000 file names. Choose a folder to search a smaller part." Search again inside a folder, or a favourite folder, to find the rest.
Google Drive
Kind: Google Drive (google_drive). No options.
Each person signs in with their own Google account through SourceLace's Google app (the same app as Gmail and Calendar), and is asked only for https://www.googleapis.com/auth/drive.readonly ("See and download all your Google Drive files"). Connecting Drive never gives SourceLace someone's mail, and connecting mail never gives it their files. Only when an admin lets agents save files here does it also ask for https://www.googleapis.com/auth/drive (see Saving files to a folder).
What your admin does in Google Workspace (Drive)
Nothing is registered: SourceLace provides the Google app. Only if your organization restricts third-party apps does your Google Workspace admin trust it, once. About 5 minutes.
Who: a Google Workspace super admin (or an admin with the Security settings privilege).
- Check whether apps are restricted. In the Google Admin console: Security → Access and data control → API controls. If Unconfigured third-party apps is set to block apps, or Drive is a restricted service, continue with step 2; otherwise there is nothing to do.
- Trust SourceLace. On the same page, Manage Third-Party App Access: find SourceLace (it is listed once anyone tried to connect; otherwise Add app → OAuth App Name Or Client ID and search for SourceLace). Set its access to Trusted (or Specific Google data, allowing Drive), and Save.
- People connect on My connections and tick the Drive box on Google's page.
Check that it worked: one person connects and asks for a file they know is in their Drive. If Google shows "unverified app" or refuses, contact support@sourcelace.com.
Google's own guide: Google Workspace Admin Help (search for "Control which third-party apps access Google Workspace data").
When something goes wrong with Google Drive
| What you see | What it means | What to do |
|---|---|---|
| "Sign-in was not completed: admin_policy_enforced. Your Google Workspace admin's policy blocks SourceLace from Google Drive ..." | Your Workspace blocks unconfigured apps, or Drive for them. | A super admin trusts SourceLace (step 2). |
| "Sign-in was not completed: access_denied. You chose Cancel on Google's page ..." | The person cancelled, or left the Drive box unticked. | Connect again and allow every permission. |
| "Google did not grant read access to Drive. Connect again and tick the box on Google's consent screen." | The Drive box was unticked. | Connect again and tick it. |
| "Your Google sign-in has expired." | The sign-in ended. | Connect again. |
| "Google Drive sent back something other than data." or "SourceLace refused to make that call to Google Drive." | Google answered with something SourceLace cannot read as data, or the call was to an address outside Google, which SourceLace never makes. | Try again shortly. If it repeats, contact support. |
SharePoint and OneDrive
Kind: SharePoint and OneDrive (microsoft_files). No options.
One source covers both: each person's OneDrive ({"action": "list"}) and every SharePoint document library they can open ({"action": "drives", "text": "sales"}). Search covers both too. File ids look like b!abc...~01XYZ...; use them exactly as returned.
Each person signs in with their own work or school account through SourceLace's Microsoft app, and approves these delegated Microsoft Graph permissions (SourceLace acts as the person, with only their access): offline_access, User.Read, Files.Read.All, Sites.Read.All; and only when an admin lets agents save files here, Files.ReadWrite.All (see Saving files to a folder).
What your admin does in Microsoft 365 (SharePoint and OneDrive)
Nothing is registered: SourceLace provides the Microsoft app. About 5 minutes.
Who: a Microsoft Entra admin who may grant tenant-wide consent (Global Administrator, Cloud Application Administrator or Application Administrator), and a Microsoft 365 admin for licences.
- Approve SourceLace once. Most organizations do not let people approve apps themselves, so the first person to connect sees Need admin approval. Connect once yourself and tick Consent on behalf of your organization, or afterwards open the Entra admin center → Enterprise applications → SourceLace → Permissions → Grant admin consent.
- Licences. People need a licence that includes SharePoint and OneDrive (most Microsoft 365 business plans do): Microsoft 365 admin center → Users → Active users → the person → Licenses and apps.
- OneDrive exists once opened. Microsoft creates a person's OneDrive the first time they open it. People who never did open onedrive.com once; their SharePoint libraries work either way.
Check that it worked: one person connects and asks for a file they know is in their OneDrive or a SharePoint library they use.
Microsoft's own guides: SharePoint documentation and Microsoft Entra documentation (search for "Grant tenant-wide admin consent").
When something goes wrong with SharePoint and OneDrive
| What you see | What it means | What to do |
|---|---|---|
| "Sign-in was not completed: AADSTS65001 ... Your Microsoft Entra admin approves SourceLace once ..." (or AADSTS90094, "Need admin approval") | Your tenant does not let people approve apps, and no admin has approved SourceLace yet. | An Entra admin grants admin consent (step 1). |
| "Microsoft sign-in failed: ..." | Microsoft's own reason follows. | Check step 1. |
| "You have no OneDrive yet: Microsoft creates it the first time you open OneDrive ..." | The person never opened OneDrive, or has no licence that includes it. | Open onedrive.com once (step 3), or give a licence (step 2). |
| "Microsoft Graph: you do not have access to that, or the sign-in lacks a permission." | The person cannot open that file or site. | Ask the site's owner for access. |
| "Microsoft Graph: not found, or you cannot see it." | The id is wrong, or the person cannot see it. | Use ids exactly as SourceLace returned them. |
| "'...' is not a SharePoint or OneDrive id. Use an id from a search, list or drives result." | The id was typed or changed. | Use ids exactly as returned. |
| "Your Microsoft session has expired." | The sign-in ended. | Connect again. |
| "SourceLace's Microsoft sign-in is not set up correctly." | SourceLace's own Microsoft app is not configured properly on SourceLace's side. | Contact support. |
| "Microsoft Graph sent back something other than data.", "Microsoft Graph returned an unexpected link." or "SourceLace refused to make that call to Microsoft Graph." | Microsoft answered with something SourceLace cannot read as data, or pointed to an address outside Microsoft Graph, which SourceLace never calls. | Try again shortly. If it repeats, contact support. |
Saving files to a folder
Agents, and you in a chat, can save the files they make (Word, PowerPoint, PDF, Excel, CSV) to one folder in Google Drive, SharePoint or OneDrive, such as a team's Weekly reports folder. Each save adds a new file as the person who runs the agent, with only their own access: if they cannot add files to the folder, neither can the agent. Nothing already in the folder is changed, replaced or deleted; a file with the same name gets a number added. The agent's owner adds a Save files to a folder action (see Sending files the agent made); each file waits for approval unless an admin allows that one folder to be saved to by itself. In a chat, you ask for the file and the folder ("Make this a Word report and save it to my Reports folder"); you see a preview with the folder and the file names and click Apply before anything is saved.
It is off until a SourceLace admin turns it on for the source, and it needs one more permission from Google or Microsoft.
Formats. You choose the format when you ask: PDF, Word, Excel, PowerPoint or CSV, saved exactly as made; or, in Google Drive, a Google Doc (made from a Word file), a Google Sheet (from an Excel or CSV file) or a Google Slides file (from a PowerPoint file). Say so in your request ("save it as a Google Sheet"), or tell an agent in its instructions. Leave it out and the file is saved as it is. Google Docs, Sheets and Slides are a Google Drive choice only; SharePoint and OneDrive save the file as made. Google turns the file into its own kind when it arrives, so complicated formatting can look slightly different from the Word or PowerPoint original; open one and check before you rely on it. If you ask for a Google Doc from a file that is not a Word file, SourceLace tells you what it needs and saves nothing.
What your admin does in SourceLace and Google Workspace (Drive)
Who: a SourceLace admin (steps 1 and 4), and a Google Workspace super admin only if your organization restricts third-party apps (step 2). About 10 minutes.
- Turn saving on. In SourceLace, Connections, open the Google Drive source, turn on Allow changes and keep
filesunder Objects that can be changed (it is filled in for you). Save. - Allow the extra Drive access, if apps are restricted. In the Google Admin console: Security → Access and data control → API controls → Manage Third-Party App Access, open SourceLace and check that its access is Trusted (or Specific Google data with Drive allowed). If you set Drive to read-only for apps, allow full Drive access for SourceLace. Save.
- People connect again. Each person who runs such an agent opens My connections, connects Google Drive again, and on Google's page ticks the box See, edit, create, and delete all of your Google Drive files. SourceLace only ever adds new files; it has no call that edits or deletes one. Google offers no narrower permission that can add a file to a folder someone else made.
- Allow saving by itself (optional). In SourceLace, Agent settings → Actions that may run without approval, add
<source>|folder:<folder id>, such asgoogle_drive:main|folder:1AbCdEf, exactly as the agent editor shows it. Only that folder then takes files without approval.
Check that it worked: run an agent with a Save files to a folder action, approve its file, and find the file in the folder in Google Drive; the run's Deliveries list says Sent. Or, in a chat, ask for a small file to be saved to the folder, click Apply on the preview, and find the file in the folder.
Google's own guide: Google Workspace Admin Help (search for "Control which third-party apps access Google Workspace data").
What your admin does in SourceLace and Microsoft 365 (SharePoint and OneDrive)
Who: a SourceLace admin (steps 1 and 4), and a Microsoft Entra admin who may grant tenant-wide consent (Global Administrator, Cloud Application Administrator or Application Administrator) if your organization does not let people approve apps themselves (step 2). About 10 minutes.
- Turn saving on. In SourceLace, Connections, open the SharePoint and OneDrive source, turn on Allow changes and keep
filesunder Objects that can be changed. Save. - Approve the extra permission once. SourceLace now also asks for the delegated permission Files.ReadWrite.All ("Have full access to all files user can access"): it acts as the person, with only their access. In the Microsoft Entra admin center: Enterprise applications → SourceLace → Permissions → Grant admin consent for your organization, or tick Consent on behalf of your organization when you connect yourself (step 3). Microsoft's narrower Sites.Selected would need an admin to grant every site to SourceLace through the Graph API, with no screen for it, so SourceLace does not use it.
- People connect again. Each person who runs such an agent connects SharePoint and OneDrive again on My connections and accepts. They also need permission to add files to the folder in SharePoint (Edit or Contribute on the library or folder: the site owner gives it under Settings → Site permissions).
- Allow saving by itself (optional). In SourceLace, Agent settings → Actions that may run without approval, add
<source>|folder:<folder id>exactly as the agent editor shows it.
Check that it worked: run an agent with a Save files to a folder action, approve its file, and find the file in the SharePoint library or OneDrive folder; the run's Deliveries list says Sent.
Microsoft's own guides: SharePoint documentation and Microsoft Entra documentation (search for "Grant tenant-wide admin consent").
Finding a folder's id
- Google Drive: open the folder in a browser. Its address is
https://drive.google.com/drive/folders/1AbCdEf...: the id is the part after/folders/. For a shared drive's top folder, use the shared drive's own address the same way. - SharePoint and OneDrive: ask SourceLace in a chat, for example "list the folders in the Sales library of SharePoint", and copy the folder's id exactly as shown (it looks like
b!AbC...~01XYZ...).b!...~rootis a library's top folder.
When something goes wrong while saving
| What you see | What it means | What to do |
|---|---|---|
| "Writes to files are turned off for ... An admin can enable them per source and object." | Saving is not turned on for the source. | A SourceLace admin turns on Allow changes with files (step 1). |
| "Google did not let SourceLace add files to Drive, which your admin turned on for agents ..." | The person did not tick Drive access on Google's page. | Connect again and tick every box (Google step 3). |
| "Google Drive: this sign-in does not allow that. Connect the source again." | The person connected before saving was turned on. | Connect again (step 3). |
| "Microsoft Graph: you may not add files to that folder, or the sign-in lacks Files.ReadWrite.All ..." | The person cannot add files there, or connected before saving was turned on, or consent is missing. | Ask the folder's owner for edit access; connect again; an Entra admin grants consent (Microsoft step 2). |
| "Sign-in was not completed: AADSTS65001 ..." (or "Need admin approval") | No admin has approved Files.ReadWrite.All yet. | An Entra admin grants admin consent (Microsoft step 2). |
| "You may not add files to the folder ... in Google Drive. Ask its owner." | The person can see the folder but not add to it. | The folder's owner shares it with them as Editor (or Contributor on a shared drive). |
| "That is a file, not a folder: choose the folder files go to." | The id is a file's. | Copy the folder's id (Finding a folder's id). |
| "Google Drive: not found, or you cannot see it." or "Microsoft Graph: that folder was not found, or you cannot see it." | The id is wrong, the folder was deleted, or the person cannot see it. | Check the id; ask for access. |
| "Microsoft Graph: that folder is full (its storage quota is used up) ..." | The site's or OneDrive's storage is full. | Free space or ask the Microsoft 365 admin for more storage, then Retry. |
| "'...' is not a file name SharePoint or OneDrive takes." | The file's name has a character SharePoint refuses (such as : or #). |
Change the document's title in the agent's instructions. |
| "Google Drive sent the upload to an unexpected address; stopping." or "Microsoft Graph sent the upload to an unexpected address; stopping." | The vendor answered in a way SourceLace does not trust. Nothing was saved. | Retry; if it keeps happening, contact SourceLace support. |
| "Google Drive asked SourceLace to wait ..." or "Microsoft Graph asked SourceLace to wait ..." (the line says Retrying) | The vendor is limiting requests. | Nothing: SourceLace tries again by itself for up to a day. |
| Needs a check on a SharePoint or OneDrive save | SourceLace restarted while saving and SharePoint cannot say whether the file arrived. | Look in the folder; press It did not arrive: send again only if it is not there. |
| "Only Word files can be saved as a Google Doc ..." (or Excel or CSV for a Google Sheet, PowerPoint for Google Slides) | The file made is not in the format that Google kind of file is made from. | Ask for the file in that format (for example a Word report for a Google Doc), or leave out the Google format to save the file as it is. |
| "save_as works only for a Google Drive folder ..." | A Google Doc, Sheet or Slides file was asked for in SharePoint or OneDrive. | Ask for a Word, Excel or PowerPoint file there. |
| "Google Drive did not finish the upload." | Google Drive stopped before it had the whole file, so nothing was saved. | Try again. If it repeats, check the folder's free space and contact support. |
Amazon S3
Kind: Amazon S3 (s3).
S3 has no per-person sign-in, so S3 access is per source, not per person. Each S3 source reads with one set of AWS credentials, and everyone who can use that source reads with that same access. The IAM policy behind those credentials decides which buckets and files the source can read. To narrow who in your organization can use an S3 source, use access by group. Until you do, everyone in your organization can use every S3 source you add, so only add buckets that everyone may read.
SourceLace makes only two kinds of S3 call, both reads: ListObjectsV2 (list and search) and GetObject (read). With a role, it also calls STS AssumeRole for short-lived credentials.
What your admin does in AWS (Amazon S3)
Once per source. About 15 minutes.
Who: an AWS admin who may create IAM policies and users or roles (and, for KMS-encrypted buckets, edit the key policy).
Each S3 source reads with your organization's own AWS access: keys you enter on the source, or a role in your AWS account that SourceLace assumes. No other organization can use either one.
-
Write down each bucket's name and region. In the S3 console, Buckets: the Name (such as
corvanta-docs, nevers3://or a link) and, on the bucket's Properties tab, its AWS Region (such aseu-west-1). Buckets in different regions need separate sources: a wrong region shows as an error naming the bucket's real region. -
Create a read-only policy. IAM → Policies → Create policy → JSON, such as (change
corvanta-docsand thereports/folder to yours; drop theConditionto allow the whole bucket):{ "Version": "2012-10-17", "Statement": [ {"Effect": "Allow", "Action": "s3:ListBucket", "Resource": "arn:aws:s3:::corvanta-docs", "Condition": {"StringLike": {"s3:prefix": ["reports/*"]}}}, {"Effect": "Allow", "Action": "s3:GetObject", "Resource": "arn:aws:s3:::corvanta-docs/reports/*"} ] }If the bucket is encrypted with a KMS key (Properties → Default encryption shows SSE-KMS), also allow
kms:Decrypton that key, and allow the user or role in the key's own key policy. -
Choose how SourceLace signs in, one of:
-
Access keys (simplest): IAM → Users → Create user, attach the policy, then Security credentials → Create access key ("Application running outside AWS"). You enter its access key ID and secret access key on the source. The secret is stored encrypted with your organization's own key and is never shown again, not even to admins: the source shows
(saved)instead. Leave the secret empty when you edit the source to keep the saved one; if you change the access key ID, enter its secret too. -
A role SourceLace assumes (no long-lived keys leave your account): IAM → Roles → Create role → Custom trust policy, attach the policy, and copy the role's ARN. In the role's trust policy, let the AWS identity that SourceLace support names assume it, with the external ID SourceLace shows for your organization. SourceLace sets this external ID itself (it looks like
sourcelace-corvanta) and always sends it, so another organization cannot use your role even if it learns the role's ARN. You find it on Connections, on any of your S3 sources after saving (aws_external_idinadmin_sources). A trust policy looks like:{ "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": {"AWS": "arn:aws:iam::<SourceLace's account, from support>:user/sourcelace"}, "Action": "sts:AssumeRole", "Condition": {"StringEquals": {"sts:ExternalId": "sourcelace-corvanta"}} }] }
You can also give a source both your own keys and a role: SourceLace then assumes the role with your keys.
-
Check that it worked: after your SourceLace admin adds the source, click Connect (there is no sign-in page) and ask for the files in a folder you know. AWS CloudTrail shows the ListObjectsV2 call.
Amazon's own guides: Amazon S3 documentation and IAM documentation.
Add the source (SourceLace admin)
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
buckets |
List, separated by commas | (required) | corvanta-docs |
The buckets this source reads, by name (step 1). s3://corvanta-docs or the console's link also works. A folder goes under prefix, not here. |
region |
Text | (required) | eu-west-1 |
The buckets' AWS region, from the bucket's Properties tab (step 1). |
prefix |
Text | (none) | reports/ |
Only read under this folder. SourceLace enforces it too, before any call. |
access_key_id |
Text | (none) | AKIAIOSFODNN7EXAMPLE |
Your IAM user's access key ID. Needed unless you use a role. |
secret_access_key |
Secret | (none) | The secret that goes with it. Stored encrypted and shown only as (saved). Best typed into Connections, not chat. |
|
role_arn |
Text | (none) | arn:aws:iam::123456789012:role/sourcelace-read |
An IAM role in your account for SourceLace to assume. |
favourite_folders |
List, separated by commas | (none) | corvanta-docs/reports/2026/ |
Up to 20 folders, written bucket/folder/, that everyone's searches look in first. Each must be inside buckets and prefix. See Finding files faster. |
search_contents |
Choice | names |
contents |
How this source is searched: names (names only) or contents (names and file contents). See How S3, Azure Storage and Google Cloud Storage are searched. |
content_folders |
List, separated by commas | (none; required with contents) |
corvanta-docs/contracts/ |
Up to 20 folders whose files may be read for a search. Each must be inside buckets and prefix. |
content_types |
List, separated by commas | Every type SourceLace reads | pdf, docx |
The file types searched inside: pdf, docx, xlsx, pptx, csv, text, html. |
A source needs either keys or a role. There is no external_id option any more: SourceLace sets it for your organization. The older keys option, which named keys kept in SourceLace's server settings, is no longer accepted.
People still click Connect once (there is no sign-in page; it only records that they connected). list_sources shows the source's access as the role, or as "the source's own access keys", never the keys themselves.
Sources added before this change that used keys from SourceLace's server settings stop working until an admin opens them on Connections and enters your own access keys, or a role. Sources with a role and an external ID you typed need your trust policy updated to the external ID SourceLace shows, and then saving again.
S3 search matches file names (reading a file you name still gives its text), and looks through up to 10,000 names per search; with Names and file contents it also searches inside the files in the folders you allow. Searching inside one folder is faster: see Finding files faster.
When something goes wrong with Amazon S3
| What you see | What it means | What to do |
|---|---|---|
| "Amazon S3: this bucket is in region ..., not the source's region. Change the source's Region to ..." | The bucket is in another region than region. |
Set Region to the region named, or make a separate source for that bucket. |
| "AWS does not know the source's access key ID ..." | The access key ID was mistyped, deleted or deactivated. | Enter an active key (step 3). |
| "The source's secret access key does not match its access key ID ..." | The secret was mistyped, or belongs to another key. | Enter the secret again, with no spaces. |
| "Amazon S3 has no bucket with that name (NoSuchBucket) ..." | A bucket name is misspelt. | Copy the name from the S3 console (step 1). |
| "... write only the bucket name under Buckets (...) and put ... under Folder." | A folder was added to a bucket name. | Put the folder in prefix. |
| "Amazon S3 refused to decrypt this file: its KMS key does not let the source's role use it ..." | The bucket is encrypted with a KMS key the source may not use. | Allow kms:Decrypt (step 2). |
| "Amazon S3 refused access (AccessDenied). The source's keys or role cannot read this; an admin can change its IAM policy." | The policy does not allow that bucket or folder. | Widen the policy (step 2) if the source should read it. |
| "AWS refused to let SourceLace assume the source's role (AccessDenied: ...). Check that role_arn is exactly the role's ARN, and that its trust policy names SourceLace's AWS account ..." | The role's trust policy or role_arn is wrong. |
Fix them (step 3). Other AWS codes are explained in the Amazon Redshift table. |
| "... needs a valid "buckets" (bucket names, separated by commas) in its options." (or "region", "access_key_id", "secret_access_key", "role_arn", ...) | That option is empty or malformed. | Fix it on Connections. |
| "... has no AWS access of its own. Enter your organization's own access keys ... or a role ... on Connections." | Neither keys nor a role is set. | Enter one (step 3). |
| "... still names the server's S3 keys, which SourceLace no longer uses to read buckets. ..." | The source was set up before each organization used its own access. | Open it on Connections and enter your own access keys or a role. |
| "... has an external ID typed by an admin. SourceLace now sets it: put sourcelace-... in your role's trust policy, then save this source again on Connections." | The trust policy uses an old external ID. | Change it to the one named, then save the source again. |
| "This SourceLace server has no AWS identity of its own, so it cannot assume roles. ..." | Roles are not set up on this server. | Use your own access keys, or ask support. |
| "Enter the secret access key that goes with the new access key ID." | The access key ID changed without its secret. | Enter its secret too. |
| "This source only reads under ...". | The file is outside the source's prefix. |
Read files inside it. |
| "Amazon S3: not found, or this source cannot see it." | The file or folder does not exist, or it is outside what the source's keys or role may read. | Use a file id from a search or list, and ask an admin to check the source's IAM policy. |
| "Amazon S3 sent back something other than data.", "AWS did not return credentials for the source's role." or "SourceLace could not tag the AWS session: a value has characters AWS refuses." | AWS answered in a form SourceLace cannot use, or the role session could not be made. | Try again shortly. If it repeats, check the role's trust policy (see What your admin does in AWS) and contact support. |
Azure Data Lake and Blob Storage
Kind: Azure Data Lake and Blob Storage (azure_storage).
One source reads one storage account: Azure Data Lake Storage Gen2 or plain Blob Storage (both answer the same Blob API). Each person signs in with their own work account, so Azure decides what they can read: their Azure roles on the account or container, and, in a Data Lake account, the access control lists on folders and files. Someone without a data role sees a clear refusal; nobody reads with anyone else's access, and no account key or SAS token is used.
SourceLace asks only for Azure Storage's delegated permission user_impersonation (plus openid, profile and offline_access to know who signed in and keep them signed in), and makes only two kinds of call, both reads: List Blobs (list and search) and Get Blob (read).
What your admin does in Azure
Once per storage account. About 10 minutes.
Who: an Azure Owner or User Access Administrator on the storage account (to assign roles and change networking), and a Microsoft Entra admin who may grant tenant-wide consent.
- Write down the account and containers. In the Azure portal, Storage accounts: the account's name (such as
corvantalake, not its address), and under Data storage → Containers, the containers to read (such asfinance). An address such ashttps://corvantalake.blob.core.windows.net/financeorabfss://finance@corvantalake.dfs.core.windows.net/also works in SourceLace. - Give people a data role. On the storage account, Access control (IAM) → Add role assignment: give Storage Blob Data Reader to the people or groups who should read through SourceLace (on the whole account or on single containers). Owner and Contributor do not include reading data.
- Data Lake folders: for an account with access control lists, also give those people read and execute on the folders they should read (Containers → the container → Manage ACL).
- Networking: if the account's Networking allows only selected networks, add SourceLace's outbound IP addresses (ask support@sourcelace.com), or Azure refuses every call.
- Approve SourceLace once (Entra admin). Most organizations do not let people approve apps themselves. Connect once yourself and tick Consent on behalf of your organization, or afterwards open the Entra admin center → Enterprise applications → SourceLace → Permissions → Grant admin consent.
- Optional: your own Entra app, to sign in through an app your organization controls instead of SourceLace's: in the Microsoft Entra admin center → App registrations → New registration, add a Web redirect URI with exactly SourceLace's redirect URL,
https://mcp.sourcelace.ai/connect/callback, add the delegated API permission Azure Storage → user_impersonation and Grant admin consent, then Certificates & secrets → New client secret and copy its Value (not the Secret ID; it is shown only once). Give the source itsclient_id,client_secretandtenant.
Check that it worked: one person connects and lists a container. The storage account's Monitoring → Logs (if diagnostic logs are on) shows List Blobs calls under their name.
Microsoft's own guides: Azure Storage documentation (search for "Assign an Azure role for access to blob data") and Microsoft Entra documentation.
Add the source (SourceLace admin)
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
account |
Text | (required) | corvantalake |
The storage account name (step 1). |
containers |
List, separated by commas | (required) | finance, sales/reports |
The containers this source reads. Add /folder to read only under that folder. |
prefix |
Text | (none) | shared/ |
Only read under this folder, in containers listed without one. |
tenant |
Text | SourceLace's setting | corvanta.onmicrosoft.com |
The Entra tenant that owns the storage account. Required with your own app; useful for guests from other tenants. |
client_id |
Text | SourceLace's app | 1a2b3c4d-... |
Your own Entra app's Application (client) ID. |
client_secret |
Secret | (none) | Its client secret's Value. Stored encrypted and never shown again. | |
favourite_folders |
List, separated by commas | (none) | finance/plans/ |
Up to 20 folders, written container/folder/, that everyone's searches look in first. Each must be inside containers and prefix. |
search_contents |
Choice | names |
contents |
How this source is searched: names (names only) or contents (names and file contents). See How S3, Azure Storage and Google Cloud Storage are searched. |
content_folders |
List, separated by commas | (none; required with contents) |
finance/policies/ |
Up to 20 folders whose files may be read for a search. Each must be inside containers and prefix. |
content_types |
List, separated by commas | Every type SourceLace reads | pdf, docx |
The file types searched inside: pdf, docx, xlsx, pptx, csv, text, html. |
File ids look like finance/plans/Corvanta plan.docx (container, then the path). Search matches file names and looks through up to 10,000 names per search; with Names and file contents it also searches inside the files in the folders you allow. Searching inside one folder is faster: see Finding files faster.
When something goes wrong with Azure Storage
| What you see | What it means | What to do |
|---|---|---|
| "Sign-in was not completed: AADSTS65001 ... Your Microsoft Entra admin approves SourceLace once ..." (or AADSTS90094, "Need admin approval") | No admin has approved SourceLace for Azure Storage yet. | Grant admin consent (step 5). |
| "The client_secret of ... looks like the secret's ID ..." | The Secret ID was copied instead of the Value. | Copy the Value (step 6), or make a new secret. |
| "Microsoft sign-in for Azure Storage failed: AADSTS7000215 ..." | Your own app's secret is wrong or expired. | Make a new secret and enter its Value (step 6). |
| "Microsoft sign-in for Azure Storage failed: ..." (another reason) | Microsoft's own reason follows. | Check steps 5 and 6. |
| "Azure Storage refused access to ... (AuthorizationPermissionMismatch): your account has no data role there." | The person has no data role on that container. | Give Storage Blob Data Reader (step 2), or read access in the access control lists (step 3). |
| "Azure Storage refused access to ... (AuthorizationFailure). The storage account's firewall or network rules may block SourceLace" | The account's network rules block SourceLace. | Allow SourceLace's IP addresses (step 4). |
| "... needs the option 'account': the storage account name ..." | account is empty or not a storage account name. |
Copy the name (step 1). |
| "The option 'containers' of ... has '...', which is not a valid name." | A container name is malformed. | Copy the names (step 1). |
| "Your Azure Storage sign-in was not accepted." | The sign-in was for another tenant. | Connect again. If it repeats, set tenant to the tenant that owns the storage account. |
| "The option 'tenant' of ... must be your Microsoft Entra tenant id or domain, such as corvanta.onmicrosoft.com." or "... uses your own Entra app, so it also needs the option 'tenant' ..." | The source signs in through your own Entra app, which needs your tenant. | An admin enters the tenant ID or domain (Entra admin center, Overview) on the source. |
| "...: client_id must be your Entra app's Application (client) ID, and client_secret one of its client secrets." | The two values were swapped, or something else was pasted in. | Copy the Application (client) ID and a secret's Value from your app registration. |
| "Azure Storage: the storage account of ... is disabled. Ask an Azure admin." | The storage account is switched off in Azure. | An Azure admin enables it. |
| "Azure Storage: the container ... does not exist. Ask an admin to fix the source." | A container named in the source's options is not in the storage account. | An admin corrects the container name in the source's options. |
| "Azure Storage: not found, or you cannot see it. Use an id from search or list." | The file does not exist, or your account has no data role on it. | Use an id from a search or list. If it repeats, ask an Azure admin about your access. |
| "Azure Storage is busy (ServerBusy). Try again in a minute." | Azure is limiting requests to the account. | Wait a minute and ask again. |
| "Azure Storage sent back something other than data." | Azure answered with something SourceLace cannot read as data. | Try again shortly. If it repeats, contact support. |
Google Cloud Storage
Kind: Google Cloud Storage (gcs).
Each person signs in with their own Google account, so Google Cloud decides what they can read: their IAM roles on the bucket (or its project), and object ACLs where the bucket uses them. Nobody reads with anyone else's access, and no service account key is used.
SourceLace asks only for https://www.googleapis.com/auth/devstorage.read_only ("View your data in Google Cloud Storage") and the person's email address, and makes only two kinds of call, both reads: objects.list (list and search) and objects.get (read). Requester-pays buckets are not read.
What your admin does in Google Cloud
Once per bucket. About 10 minutes.
Who: a Google Cloud admin with Storage Admin (or Project IAM Admin) on the bucket's project, and, if your Workspace restricts apps, a Google Workspace super admin.
- Write down the bucket names. In the Google Cloud console, Cloud Storage → Buckets: each bucket's Name (such as
corvanta-docs).gs://corvanta-docsor the console's link also works in SourceLace. - Give people read access. Choose the bucket, then Permissions → Grant access, and give Storage Object Viewer to the people or groups who should read through SourceLace.
- Workspace app access: if your Google Workspace restricts third-party apps, a super admin trusts SourceLace's app under Google Admin console → Security → Access and data control → API controls → Manage Third-Party App Access (as for Google Drive).
- VPC Service Controls: if the project is inside a service perimeter, add an ingress rule that lets the people read Cloud Storage from outside it, or Google refuses every call.
- Optional: your own OAuth client, to sign in through a client your organization controls: in the Google Cloud console, APIs & Services → Credentials → Create credentials → OAuth client ID, type Web application, with exactly SourceLace's redirect URL,
https://mcp.sourcelace.ai/connect/callback, as an authorized redirect URI. In Google Auth Platform → Data access, add the scopedevstorage.read_only. Under Audience, choose Internal (or publish the app to In production): in Testing, only listed test users can sign in and sign-ins end after 7 days. Enable the Cloud Storage JSON API in that project (APIs & Services → Library). Give the source itsclient_idandclient_secret.
Check that it worked: one person connects and lists a bucket. Cloud Audit Logs (data access logs, if turned on) show the objects.list call under their name.
Google's own guide: Cloud Storage documentation (search for "IAM roles for Cloud Storage").
Add the source (SourceLace admin)
| Option | Type | Default | Example | What it is |
|---|---|---|---|---|
buckets |
List, separated by commas | (required) | corvanta-docs, corvanta-finance/reports |
The buckets this source reads (step 1). Add /folder to read only under that folder. |
prefix |
Text | (none) | shared/ |
Only read under this folder, in buckets listed without one. |
client_id |
Text | SourceLace's client | 1234567890-abc.apps.googleusercontent.com |
Your own Google OAuth client's ID (step 5). |
client_secret |
Secret | (none) | Its client secret. Stored encrypted and never shown again. | |
favourite_folders |
List, separated by commas | (none) | corvanta-docs/shared/2026/ |
Up to 20 folders, written bucket/folder/, that everyone's searches look in first. Each must be inside buckets and prefix. |
search_contents |
Choice | names |
contents |
How this source is searched: names (names only) or contents (names and file contents). See How S3, Azure Storage and Google Cloud Storage are searched. |
content_folders |
List, separated by commas | (none; required with contents) |
corvanta-docs/contracts/ |
Up to 20 folders whose files may be read for a search. Each must be inside buckets and prefix. |
content_types |
List, separated by commas | Every type SourceLace reads | pdf, docx |
The file types searched inside: pdf, docx, xlsx, pptx, csv, text, html. |
File ids look like corvanta-docs/shared/plan.docx (bucket, then the path). Search matches file names and looks through up to 10,000 names per search; with Names and file contents it also searches inside the files in the folders you allow. Searching inside one folder is faster: see Finding files faster.
When something goes wrong with Google Cloud Storage
| What you see | What it means | What to do |
|---|---|---|
| "Sign-in was not completed: admin_policy_enforced. Your Google Workspace admin's policy blocks SourceLace from Google Cloud Storage ..." | Your Workspace blocks unconfigured apps, or Cloud Storage for them. | A super admin trusts SourceLace (step 3). |
| "Sign-in was not completed: access_denied. You chose Cancel on Google's page ..." | The person cancelled, or left a box unticked. | Connect again and allow every permission. |
| "Google did not grant read access to Cloud Storage." | The Cloud Storage box was unticked. | Connect again and tick it. |
| "Google Cloud Storage refused access to bucket ...: ..." | The person has no role on that bucket. | Give Storage Object Viewer (step 2). |
| "The Cloud Storage JSON API is turned off in the Google Cloud project of the source's OAuth client ..." | Your own OAuth client's project does not have the API on. | Enable it (step 5). |
| "Google Cloud's VPC Service Controls block access to bucket ... from outside your perimeter ..." | The bucket's project is inside a service perimeter. | Add an ingress rule (step 4), or remove the bucket from the source. |
| "Google Cloud Storage: not found in bucket ..., or you cannot see it ..." | The file or bucket does not exist, or the person cannot see it. | Use ids from a search or list; check the bucket names (step 1). |
| "The option 'buckets' of ... has '...', which is not a valid name." | A bucket name is malformed. | Copy the names (step 1). |
| "Google Cloud Storage: bucket ... is a requester-pays bucket, which SourceLace does not read ..." | Requester-pays buckets are not read. | Remove it from the source. |
| "Your Google sign-in for Cloud Storage has expired. Connect again." (every week) | Your own OAuth client is still in Testing, where sign-ins end after 7 days. | Set its Audience to Internal, or publish it (step 5). |
| "...: client_id must be your Google OAuth client's ID (ending in .apps.googleusercontent.com), and client_secret its client secret." | The client ID or secret in the source is not from a Google OAuth client. | An admin copies both from the OAuth client in the Google Cloud console (APIs & Services, Credentials). |
| "Google Cloud Storage is busy. Try again in a minute." | Google is limiting requests. | Wait a minute and ask again. |
| "Google Cloud Storage sent back something other than data." | Google answered with something SourceLace cannot read as data. | Try again shortly. If it repeats, contact support. |
When something goes wrong
Each system above has its own table. For all of them:
| What you see | What to do |
|---|---|
| "'...' is ... MB; SourceLace reads files up to 25 MB." | The file is too large to read. |
| "The PDF is password-protected, so SourceLace cannot read it." | Remove the password, or read it another way. |
| "SourceLace could not read the text in '...': the file looks damaged or is in an unexpected format" | The file could not be read; open it in its own app to check. |
| "'...' is a folder. List it with ..." | Use list on a folder, read on a file. |
| "Searched the first 10,000 file names. Choose a folder to search a smaller part." | The answer is incomplete. Search again inside a folder, or add the folder to your favourite folders. |
| "The favourite folder '...' of ... is not inside the places it reads (...). Write it as bucket/folder/." | Fix favourite_folders on Connections: each folder must be inside the source's buckets and folder. |
| "Searched inside the first 200 files, as many as one search reads. Choose a smaller folder to search the rest." (or "until 50.0 MB were read", "for 20 seconds") | The answer is incomplete. Search again inside a smaller folder. |
| "File contents are searched only in .... Choose one of them, or search names only with "match": "name"." | The folder you chose is outside the folders the admin allowed. Choose one of them, or search names only. |
| "... searches file contents, so it needs the option 'content_folders' ..." or "The folder '...' to search inside of ... is not inside the places it reads (...)" | Fix Folders whose files may be read on Connections: each must be inside the source's buckets and folder. |
| "... of the files could not be read (damaged, password-protected or not allowed), so their contents were not searched." | Those files were skipped; the rest were searched. Open them in their own app to check. |
| "'...' is not a folder in this source (...). Choose one from the list." | Choose a favourite folder from the list on My connections; it must be inside the source. |
| "'...' is not in this source's buckets (...)." | The folder is in a bucket the source does not list. |