You rename a ChatGPT Project from Q3 Sales Research to Q3-Q4 Sales Research, click the old share link from your handover doc, and get a 404 — or the link opens but shows an old read-only snapshot that’s missing your new files, or it throws “You don’t have access to this project.”
Fastest fix: open the Project, click the Share button at the top, and confirm it still says Anyone with a link (not Only those invited); copy the current link straight from that dialog and re-test it in an incognito window. Renaming alone does not rotate a shared-Project link in the current build, so if the old URL is dead the real cause is almost always cache, a toggled share setting, or an access-scope change — diagnose with the table below before you regenerate anything.
First, know which sharing model you’re on
OpenAI rolled collaborative Shared Projects out to all logged-in users by October 24, 2025 (it began as a Business-only feature in September 2025). This changed how Project links behave, so the right fix depends on which kind of link you have. As of June 2026:
| Link type | What it looks like | Renaming the Project… | Who can open it |
|---|---|---|---|
| Shared Project (collaborative) | Membership-gated project link, requires a logged-in ChatGPT account | Does not rotate the link; the project keeps its stable internal ID | Anyone you invited, or “Anyone with a link” if you set that |
| Shared chat inside a Project | chatgpt.com/share/<id> (a frozen, read-only snapshot of one conversation) | No effect on the snapshot, but the snapshot never updates either | Anyone with the URL, logged in or not |
Most “rename broke my link” reports are actually one of: a cached old URL, the share scope sitting at Only those invited, sharing that got toggled off, or a workspace move. Use the diagnosis table to land on the right one.
Diagnose: which bucket are you in?
| Symptom when you open the old link | Most likely cause | Jump to |
|---|---|---|
| 404 in your browser, but it loads fine in incognito | Browser/proxy cache or a stale tab | Step 1 |
| ”You don’t have access to this project” | Scope is Only those invited, or sharing was toggled off | Step 2 |
| Opens but files/instructions are missing or out of date | You shared a single chat snapshot, not the live Project | Cause 3 |
| 404 everywhere, link ends in the old name slug | Old slug no longer resolves (legacy snapshot links) | Step 3 |
| 404 and the Project also vanished from your sidebar | Project archived, or filtered out of the default view | If still broken |
| Link root changed entirely (personal vs Team) | Project moved between workspaces | Cause 5 |
Common causes
1. Browser or proxy cache returns the old URL
If you bookmarked the URL or your browser autocompletes from history, you can keep hitting a stale entry after a rename, get a cached 404, and assume the Project is broken.
How to spot it: the same URL works in an incognito window but fails in your normal one. Pure cache — fix the cache, not the link.
2. Share scope is “Only those invited,” or sharing was toggled off
The current Share dialog has two access levels: Only those invited and Anyone with a link. If it’s set to Only those invited, anyone not on the invite list gets an access error rather than the project. Toggling sharing off and back on can also reset the audience.
How to spot it: the link returns “You don’t have access” rather than a 404.
3. You shared a single chat snapshot, not the live Project
Sharing one conversation from inside a Project creates a frozen, read-only chatgpt.com/share/<id> snapshot. It captures that chat at that moment — it never picks up files or instructions you add later, and renaming the Project doesn’t touch it.
How to spot it: the old link still opens, but the content is missing your latest uploads or instruction edits.
4. Old slug-style link no longer resolves
Some older Project URLs carried the project name as a trailing slug (.../q3-sales-research). If your link is one of these and now 404s, the slug it encoded is gone. The collaborative Shared Project link does not work this way — it’s membership-gated and keeps a stable internal ID across renames — so the fix is to grab the current link from the Share dialog rather than reusing the slug URL.
How to spot it: the old URL ends in a slug matching the old name and 404s in incognito too.
5. Project was moved between workspaces (Team / Business / Enterprise)
Moving a project from your personal account into a Team/Business workspace changes the URL root entirely, and old personal links can’t resolve to a workspace-scoped resource. Project sharing in team workspaces is a paid-workspace feature (Business is roughly $30/user/month as of June 2026).
How to spot it: the working link root differs from the old one (personal vs workspace).
Shortest path to fix
Step 1: Test the old link in incognito before assuming it’s broken
Open a private window and paste the old URL. If it loads, your normal browser had a cached redirect or a stale tab — clear the cache or hard-reload, and you’re done. If it 404s in incognito too, the link is genuinely broken; continue.
Step 2: Open the Share dialog and copy the current link
In the Project, click the Share button at the top. Check the access level:
- For a teammate-only handoff, keep
Only those invitedand add their email so they’re on the list. - For a link anyone with the URL can open, switch to
Anyone with a link.
Set each person’s role to Can chat (view files/instructions and start chats) or Can edit (also change instructions and add/remove files). Then copy the link from this dialog — that’s always the live URL. Test it once in incognito.
Note: a collaborator opening a Shared Project must be signed in to a ChatGPT account. “Anyone with a link” means any logged-in user with the URL, not the fully anonymous public access you get from a
/share/<id>chat snapshot.
Step 3: If your old link was a slug URL, stop reusing it
Don’t try to patch the old slug. Take the membership-gated link from the Share dialog and use that everywhere. It’s stable across future renames.
Step 4: Pick stable names you won’t need to rename
Avoid embedding dates or scopes you may extend (Q3 becoming Q3-Q4). Use scopeless names like Sales Research 2026 or Customer Onboarding. A name that doesn’t encode time-bound scope rarely needs renaming, which removes the whole problem.
Step 5: Update every place the old URL was posted
Search Slack, Notion, email, and your handover doc, and replace old links with the current one. If your team treats Project URLs as long-lived references, post the new link in the same thread so the change is auditable.
Step 6: Verify with a second account
Have a teammate (or a second account) open the link. Confirm they’re prompted to join / can read the project and see the latest files. This rules out account-specific permission caching.
How to confirm the fix
After copying the current link, run this verification triple:
- Open it in your normal browser — it loads.
- Open it in incognito — it still loads (no session-dependent quirks).
- A second account or teammate opens it — they can join and read it.
All three pass: the link is safe to publish. If the second or third check fails, the share scope didn’t apply the way you intended — reopen Share and confirm the audience (Anyone with a link vs Only those invited) and each member’s role match what you want.
Prevention
- Treat Project renames as low-risk but not zero-risk: after any rename, reopen
Shareand copy the link fresh rather than trusting a URL you pasted weeks ago. - Before sharing a Project link, test it in incognito so you know it works without your session.
- For long-lived references (handover docs, runbooks), don’t paste raw URLs. Paste the Project name plus a short instruction like
search Projects for "Sales Research 2026"so readers resolve the link themselves and always reach the live version. - If you run many Projects, keep a central index doc with
name | owner | current share URL | last verified dateand update it on every rename. - For mission-critical handoffs, prefer a Team/Business workspace Shared Project over a personal-account link — workspace projects survive ownership changes and give you
Can chat/Can editroles per person.
Rename checklist
- Note the old name and link in your change log.
- Rename the Project.
- Open
Share, confirm the access level and roles, and copy the current link. - Test the link in incognito.
- Update every posted reference.
- Notify anyone who had the old link — a copied link is not retroactive; people who saved the old URL still have it.
If still broken
- Confirm the Project isn’t archived. Archived Projects can return a 404 for their link even when the owner can still see them in the workspace.
- Confirm your workspace tier. Some Enterprise tenants disable external sharing entirely, so the link only resolves for tenant members.
- If the Project vanished from your sidebar after the rename, search by the old name once: Projects are filtered by recent activity and a rename can push one out of the default view.
- Make sure you’re sharing the Project itself, not one chat inside it —
chatgpt.com/share/<id>chat snapshots and Project links are different URLs with different lifetimes. - Last resort: duplicate the Project under the new name, copy files and instructions across, retire the old one, and share the new Project link going forward.
- Still stuck: file a ticket at help.openai.com with the old URL, the new URL, and a screenshot showing both. Share-link bugs are tracked separately from general Project bugs.
Common pitfalls
- Renaming on mobile vs desktop can render the project title differently — always confirm the live link from the
Sharedialog on the client your users will use, not from a guessed URL. - A copied link is not retroactive: anyone who saved the old URL still has the broken one. Push the new link through the same channel you originally used.
- Custom GPTs are a different feature from Projects. A published GPT does carry a name-based slug in its URL, so renaming a GPT can change its public link — that’s the case where the “rename breaks the slug” rule genuinely applies.
FAQ
Does renaming a ChatGPT Project change its share link?
No. As of June 2026, the collaborative Shared Project link is membership-gated and keeps a stable internal ID, so a rename doesn’t rotate it. If your old link died after a rename, the cause is almost always cache, a Only those invited scope, sharing toggled off, or a workspace move — not the rename itself.
Why does the old link say “You don’t have access”?
The Share scope is set to Only those invited and the opener isn’t on the invite list, or sharing was toggled off. Open Share, switch to Anyone with a link or add the person’s email, then re-copy the link.
Why does the shared link open but show old files?
You shared a single chat as a chatgpt.com/share/<id> snapshot, which is frozen at the moment of sharing and never updates. Share the Project itself from the Share button instead so collaborators always see the live files and instructions.
Do people need a ChatGPT account to open my shared Project?
Yes. Opening a Shared Project requires being signed in to a ChatGPT account. Only a /share/<id> chat snapshot is viewable fully anonymously.
Is Project sharing free?
Sharing a Project to collaborators rolled out to all logged-in users in late October 2025. Sharing Projects inside a team workspace is a paid-workspace feature (Business is around $30/user/month as of June 2026).