AI Shortcut: How to Collaborate on Claude Projects Without a Teams or Enterprise License
I’m increasingly finding Claude useful to tell me how to best use Claude.
I’m working on a project right now with a bunch of colleagues, and one of the limitations of Claude, even the Pro version, is that there is no option to invite other Claude users to collaborate on a project. In order to do that, you have to upgrade everyone to a Claude Team or Enterprise license — which may not be feasible for cost or logistical reasons.
Our specific use case: a few of my Markup AI colleagues and I are vibe coding an app together in Replit (I can’t wait to tell you about it when it’s further along), and we are doing a bunch of the design work in Claude. While Replit is collaborative, Claude is not. All of the initial work on the project was done inside one person’s Claude instance and wasn’t shared.
So after a lot of back and forth with Claude, here’s the workaround we landed on.
The Core Idea
Use Google Drive as your shared brain. Use Claude’s Custom Instructions as the mechanism that loads it at the start of every conversation.
Each person keeps their own Claude Project. But instead of context living in isolation inside each person’s account, it lives in three shared Google Docs that every team member’s Claude reads from automatically.
The Three-File Architecture
Create a folder in Google Drive — something like [Project Name] / Claude Context — and put three Google Docs in it:
ProjectContext — everything Claude needs to know about the project. What it is, key decisions, the framework you’re working within, roles, terminology, things that have been explicitly decided and shouldn’t be revisited. If you hired a really smart person tomorrow and handed them one document, this is that document.
WorkingConventions — how you want Claude to behave. Communication style, output format, tools and tech stack, things Claude should never assume, any role-specific preferences individual team members have.
ChangeLog — a running dated log of decisions, newest at the top. When the full ProjectContext hasn’t been updated yet, this captures what’s new. It’s the lightweight sync mechanism that keeps things from getting stale between major updates.
Use consistent, searchable names — we use [ProjectName]_ProjectContext, [ProjectName]_WorkingConventions, and [ProjectName]_ChangeLog. Exact naming matters because Claude searches for them by name.
The Custom Instructions
Every team member pastes this into their Claude Project settings (Project → Settings → Custom Instructions):
You are working on [PROJECT NAME].
At the start of every conversation, before responding to anything
else, search Google Drive for these three files and read all of
them in this order:
1. [ProjectName]_ProjectContext — the full framework, key
decisions, architecture, and all settled decisions.
This is the source of truth.
2. [ProjectName]_WorkingConventions — how to work with this
team: communication style, output preferences, and
what not to do.
3. [ProjectName]_ChangeLog — the running log of recent
decisions. Read this to catch anything decided since
the context doc was last updated.
These files are in Google Drive under [Folder Name]. Do not
rely on training data or assumptions about this project. Always
ground responses in the current versions of these documents.
After reading them, proceed without narrating that you have
done so — just apply the context.
The “proceed without narrating” line matters. Without it, Claude opens every response with a paragraph about how it just searched Drive and found the files and read them all carefully. Gets old fast.
You can layer personal preferences on top of the shared core. The shared instructions load the shared context; any personal additions shape how Claude works with you specifically.
The Google Drive Connector
Each team member needs the Google Drive connector active in their Claude instance, authenticated to the Google account where the files live. In claude.ai, this is under Settings → Integrations.
Here’s the thing that tripped us up: the connector authenticates to a single Google account per user. If your project files live in a Google Workspace account and someone’s connector is pointed at their personal Gmail, they won’t find anything. Make sure everyone connects to the right account before you waste time debugging. The workaround here (yes, the workaround nested inside the workaround) is to use Google Drive to sync a version of your files locally one of your two Drives, then use the FileSystem connector instead of the Google Drive connector, and make sure you note that clearly in your version of the Instructions.
Verify It’s Working
Before doing any real work, each team member should run this as their first message in the new Project:
Context load test. Search Google Drive for
[ProjectName]_ProjectContext, [ProjectName]_WorkingConventions,
and [ProjectName]_ChangeLog and read all three. Then answer
these questions from what you read — no assumptions, only
what's in the documents:
[Insert 3-5 questions whose answers are clearly in your
ProjectContext]
After answering, report: which files did you find, and were
there any you couldn't locate?
Design the questions so a correct answer requires actually reading the content — not something Claude could guess from the project name alone. If it gets the answers right and reports all three files found, you’re good.
Keeping It Current
This only works if the documents stay current. Two habits make that sustainable without it becoming a chore:
The ChangeLog is the low-friction entry point. Decision gets made? Throw a dated one-liner into the ChangeLog. Don’t worry about updating the full ProjectContext every time — that can wait for the weekly pass.
The weekly harvest prompt. Once a week, run this in your Project:
Weekly context harvest. Search my recent conversations in
this project from the past 7 days. Identify any decisions,
framework changes, or structural updates that were reached
in those conversations but are not yet reflected in the
three context files in Google Drive.
For each item you find, give me:
1. What was decided or clarified
2. Which file it belongs in
3. The exact text to paste in, formatted and ready to copy
Group your output by file so I can do three copy-paste
operations total. If nothing new was decided this week,
tell me that explicitly.
Post the output to a shared Slack channel. One person — we call them the context owner — consolidates and pastes into the Drive files. Everyone’s Claude picks up the updates on the next conversation.
What This Does and Doesn’t Do
It does:
- Give every team member’s Claude the same foundational context, automatically
- Keep that context current through a lightweight weekly process
- Require zero engineering, no special plan, no new tools
- Scale easily — adding a new person is just “set up a Project and connect Drive”
It doesn’t:
- Enable real-time collaboration (Claude still can’t see what’s happening in someone else’s conversation)
- Write decisions back to Drive automatically (the connector is read-only; you still copy-paste updates by hand)
- Share personal memory across team members
Quick-Start Checklist
- Create a Google Drive folder:
[Project] / Claude Context - Create three Google Docs:
[Project]_ProjectContext,[Project]_WorkingConventions,[Project]_ChangeLog - Write the content for each — ProjectContext first, that’s where the real work is
- Each team member: create a Claude Project, paste the Custom Instructions, connect Google Drive to the right account
- Each team member: run the test prompt to verify all three files load
- Designate a context owner and pick a weekly harvest day
- Set a recurring Friday reminder
It’s not a perfect substitute for native collaboration — Anthropic, if you’re reading this, please just build multi-user Projects — but it’s a surprisingly effective workaround that costs nothing and takes about an hour to set up.
Have you found other ways to get Claude to collaborate across multiple accounts? I’d love to hear what’s working.