in this guide
Picture a 90-person consultancy. A senior account manager builds a custom assistant to draft proposals faster. She uploads the pricing sheet, three past proposals, the rate card for subcontractors and a list of client contacts. It works well, so she shares it with the sales team. Someone on that team forwards the link to a partner agency, because the assistant would help them too.
Every one of those files has its own permissions in Drive or SharePoint, set years ago by people who thought about it. None of them apply anymore. The assistant holds copies, and the assistant’s share button now decides who can read them.
That is the mechanism. A custom GPT, a Gemini Gem, a Microsoft 365 Copilot agent, a Copilot Studio agent and a Claude project all bundle instructions with knowledge. Uploading a file into one makes a second copy with a second audience. The shadow AI guide covers the paste into a chat window. This guide picks up where the paste becomes a tool other people use.
one file, two audiences
the file in the drive
what the owner set up
- Shared with the finance folder
- Changes when the folder's members change
- Shows up in the sharing report
- Deleted when the folder is cleaned up
the copy inside the assistant
what the builder chose
- Readable by anyone who can use the assistant
- Audience set by one share button
- Not in any file sharing report
- Stays until someone deletes the assistant
the vendors say it plainly
This is documented behaviour, and the documentation is direct about it.
Google. Its Gemini help page on sharing Gems says any instructions and files uploaded to a Gem can be viewed by any user with access to the Gem, and adds a warning: “don’t share the Gem with anyone who you don’t want to view the files.”
Microsoft. The Agent Builder documentation for Microsoft 365 Copilot says that when you upload files as knowledge, any user who has access to the agent also has access to the information in them. It also notes that Microsoft Purview Information Barriers, the feature some firms use to keep teams apart, does not apply to those uploaded files.
OpenAI. A custom GPT can hold up to 20 files of up to 512 MB each, per OpenAI’s help page on creating GPTs. Anyone who can chat with the GPT is talking to something that has read all of them.
Anthropic. On Claude Team and Enterprise plans, a member with “Can view” access to a project can see its contents, knowledge and instructions, per the Claude help page on project sharing.
The file kept its permissions. The copy got new ones.
how far each share button reaches
The widest setting is where the risk sits, and it differs by product. From each vendor’s own documentation:
the widest audience each builder offers
- custom GPTanyone with the link, or listed in the GPT Store, where the plan and workspace allow it
- Gemini Gemanyone with the link without signing in, or public and searchable on Google; work accounts may not see the public option
- Copilot Studio agentwith "No authentication", anyone who has the link can chat
- Agent Builder agenteveryone in the tenant, through an org-wide toggle
- Claude projecteveryone in the organization, the widest of its two visibility options on Team and Enterprise plans
reaches people outside the team that owns the files
A few details from the same pages matter in practice:
- GPT permissions come in three levels. OpenAI lists Can chat, Can view settings and Can edit. Public link sharing and the GPT Store support only Can chat.
- Gems follow Drive. Google’s admin help says shared Gems are stored and shared in Drive, so Drive’s sharing settings apply. Google’s September 2025 launch post put it bluntly: if Drive content can be shared outside the organization, Gems can too. The same post said Gem sharing would be on by default. The guest accounts guide covers what those Drive settings allow.
- Copilot Studio says when nobody is checking. Microsoft’s authentication page says that with “No authentication” you cannot control which users in your organization can chat with the agent, and that classic chatbots are configured without authentication by default. A data policy in the Power Platform admin center can require authentication.
- Agent Builder’s admin switch starts open. The default in the Microsoft 365 admin center is “All users”, so everyone can share agents with the whole organization until an admin narrows it.
what research has pulled out of them
Two pieces of research show the copy can leave the assistant.
The files came back out, word for word. In November 2023, researchers at Northwestern University tested 216 custom GPTs with crafted prompts. They report a 97.2% success rate at extracting the builders’ instructions and a 100% success rate at retrieving uploaded files, the latter across the 24 GPTs in the sample that had files, by the paper’s own table. One prompt simply asked the GPT to convert its file to markdown for download. The authors say they disclosed the findings to OpenAI before publishing. The sample is small and the product has changed since 2023, so treat the numbers as a demonstration. The lesson that holds: instructions do not keep a file in. An assistant that can quote a file can be asked to quote all of it.
Agents were left open to the internet. At Black Hat in August 2024, Michael Bargury of Zenity, a company that sells security tooling for these platforms, said Copilot Studio’s earlier default settings published bots to the web without any sign-in. “We scanned the internet and found tens of thousands of these bots,” he told The Register. That count is a vendor researcher’s claim and the article gives no method. Bargury also said the safer defaults applied only to new installations. Microsoft told The Register it was investigating the reports.
The ChatGPT shared-chat links that ended up in Google in 2025 are the same pattern one layer down: a share control that reached further than the person clicking it expected. The record is on the indexed chats page.
linked knowledge behaves differently
Some builders can point at files instead of uploading them. Microsoft’s Agent Builder can use SharePoint and OneDrive files, folders and sites. Here Microsoft’s documentation says the agent respects the end user’s own permissions: if someone cannot open a file, the agent leaves it out of their answers.
That sounds safe, and two details complicate it.
Sharing the agent can share the files. When an owner shares an agent with specific people, Agent Builder can share the selected SharePoint files and folders with them at the same time, if the owner has the rights to do so. The person gets access to the file itself, outside the assistant.
Removing someone from the agent leaves the files shared. Microsoft’s page says so directly: removing a user’s access to the agent does not affect their access to the shared files or folders. Those grants stay in SharePoint until someone removes them there. The SharePoint guide explains why grants like these pile up.
Permission-respecting retrieval also inherits whatever oversharing already exists. The Copilot audit guide covers that half, and the RAG index guide covers the version where a company builds its own index.
when the builder leaves
An assistant built by one person keeps working after that person changes role or leaves. The vendors handle ownership in different ways:
- ChatGPT workspaces. If a GPT’s owner is removed through the normal workspace flow, ownership moves to a workspace owner and the GPT is marked unassigned for review, per OpenAI’s admin help. That is a prompt to look. The GPT and its audience stay as they were.
- Agent Builder. Agents can have several owners with equal rights, and admins can reassign ownership. Anyone with “Can edit” can turn on org-wide sharing.
- Gems. Shared Gems live in Drive, so they follow what happens to the builder’s Drive files when the account is offboarded.
- Claude projects. Archiving a project keeps its members, permission levels and knowledge, per Anthropic’s help page. Access ends when someone removes it.
Admin switches have the same limit everywhere: they act on new sharing. Microsoft says changes to its control apply only to new sharing actions. Google says Gems shared before sharing was turned off remain accessible and shareable from Drive. Anthropic says existing project shares stay in place when sharing is turned off, though public projects become private. Turning the switch off leaves the old shares to be cleaned up by hand.
the migration is an inventory you get for free
Two of these products are being replaced right now, and the replacement carries the files forward.
OpenAI is retiring custom GPTs. Its migration FAQ gives 11 December 2026 as the standard retirement date, with 11 February 2027 for FedRAMP workspaces and approved deferrals. New GPT creation ended for affected Enterprise workspaces on 26 October 2026. Migration turns a GPT into a plugin and copies its knowledge files into the plugin’s reference files. The plugin starts private, and public sharing settings do not carry over. After migration the original GPT becomes read-only and its creator cannot delete it. Pulling the full list of GPTs in a workspace for bulk migration needs a workspace Owner.
Google is replacing Gems with skills. Its admin help says skills fully replace Gems no sooner than 1 March 2027 for business and enterprise plans. Converted skills keep their instructions and uploaded knowledge files, and Drive permissions and sharing settings on the original Gems transfer to the new skills.
So in one case the files move and the audience resets. In the other, the files move and the audience moves with them. Either way, someone at your company will be asked which assistants matter. That list is the inventory you never had: every assistant, who built it, which files are inside, and who can reach it.
Which assistant at your company holds a file that its original owner would never have shared with everyone who can open it?
on the record
all myths →sources
- OpenAI Help Center: Sharing and publishing GPTs
- OpenAI Help Center: Custom GPT retirement and migration FAQ
- OpenAI Help Center: Creating and editing GPTs
- OpenAI Help Center: Managing GPT access in Enterprise and Edu workspaces
- Google Gemini Apps Help: Share a Gem from Gemini Apps
- Google Workspace Admin Help: Turn Gem sharing on or off
- Google Workspace Updates: Introducing Gems sharing in the Gemini app, including admin controls (18 September 2025)
- Google Workspace Admin Help: About the transition from Gems to skills
- Microsoft Learn: Share and manage agents built in Agent Builder
- Microsoft Learn: Add knowledge sources to an agent in Agent Builder
- Microsoft Learn: Configure user authentication in Copilot Studio
- Claude Help Center: Manage project visibility and sharing
- Yu et al., Northwestern University: Assessing Prompt Injection Risks in 200+ Custom GPTs (arXiv 2311.11538, v2 May 2024)
- The Register: Copilot Studio vulnerabilities at Black Hat (8 August 2024)
