You generated a share link for a Project, pasted it into Slack, and your teammate gets “Page not found” or “You do not have permission to view this Project.” Project sharing has stricter rules than chat sharing — links are bound to your workspace, the recipient often needs to be a member of the same Team / Enterprise org, Files frequently do not travel with the link, and stale share URLs from old UI versions silently 404. Sort which of these you hit first; the fix is different for each.
Common causes
Ordered by hit rate, highest first.
1. Recipient is not in your Team / Enterprise workspace
The most common 404. Project share inside a Team workspace requires the viewer to be a member of that workspace. A personal-account teammate clicking your Team Project link gets either 404 or “request access.”
How to spot it: Recipient sees a sign-in screen, signs in with their personal account, then 404. Switching to their Team account (if they have one) resolves it.
2. Share link generated for a Project that has been renamed or moved
If you copied a link, then renamed / moved the Project, the underlying ID may still resolve — but some redirects break, especially after the Project moves between workspaces.
How to spot it: The owner can open the link fine; the recipient cannot. The owner copies a fresh link from the current Project menu and it works.
3. Share link is for a single chat, not the Project
Chat share and Project share are different actions. People copy a chat URL and call it the Project link — recipient gets the chat (or a 404 if the chat is private) but not the Project framework.
How to spot it: URL contains /c/ or /share/ (chat) instead of the Project route — wrong link type.
4. Files do not travel with the share link
Even when sharing works, Project Files are not always visible to recipients on Plus-to-Plus or cross-workspace shares. They see Instructions and chats but not the file panel.
How to spot it: Recipient says “I see the Project but can’t open the PDFs” — that is by design for many share modes.
5. Sharing was disabled at the workspace level
Team / Enterprise admins can disable external sharing entirely. The “Share” button appears, generates a link, but the link 404s outside the org.
How to spot it: Workspace admin policy page shows sharing disabled, or admin confirms restriction.
6. Recipient is signed into a different ChatGPT account in their browser
They have a personal account and a work account; the browser auto-signed them into the wrong one for this share. Result: 404 or permission error.
How to spot it: Recipient opens the link in incognito and signs in with the matching account — works.
Before you start
- Confirm whether you and the recipient are in the same workspace, or in separate workspaces.
- Have the recipient send you a screenshot of the exact error page (URL bar visible).
- Check Settings → Workspace → Sharing settings if you are on Team / Enterprise.
Info to collect
- Full share URL (mask any token if posting publicly).
- Owner workspace + plan; recipient workspace + plan.
- Screenshot from recipient side, URL bar visible.
- Whether you used “Share Project” or “Share chat” — confirm exactly.
- Date the share link was generated (in case it has expired or the Project moved).
Shortest fix path
Ordered by ROI. Steps 1 and 2 resolve most cases.
Step 1: Confirm the recipient is signed into the correct account
Tell the recipient:
1. Open the share link in a NEW incognito / private window.
2. When prompted, sign in with the account that matches our org
(work email, not personal).
3. If a workspace switcher appears, choose the same workspace
as mine.
4. Try the link again.This resolves ~50% of “404 on first click” cases.
Step 2: Regenerate the share link from the current Project
Owner side:
Open Project → top-right ... menu → Share
→ Revoke any old link
→ Generate new link
→ Paste fresh link into Slack / emailOld links from previous UI versions or pre-rename Project states often 404. A fresh link sidesteps that.
Step 3: Add the recipient to your workspace if needed
If the recipient is outside your Team / Enterprise:
Settings → Workspace → Members → Invite
→ Enter their email → assign role
→ Wait for them to accept (check spam folder)
→ Reshare the link after they acceptCross-workspace sharing is restricted on most plans; making them a member is the cleanest path.
Step 4: For files, export and re-attach
Since Files often do not travel:
Project → Files → Download all → zip → send via Slack / email
→ Recipient: create their own Project, upload the files,
paste your Instructions text from a separate shareAnnoying but reliable. For repeated handoffs, use a shared Google Drive folder as source-of-truth instead of Project Files.
Step 5: Check workspace sharing policy
Team / Enterprise admin:
Admin Console → Workspace settings → Sharing
→ Confirm "External sharing" is enabled
→ If disabled, decide whether to enable or use an internal-only
alternativeIf your admin keeps sharing off for policy reasons, sharing externally simply will not work — switch to file export.
Step 6: Use a Custom GPT for cross-org sharing
Custom GPTs (Plus+) have different share semantics — published GPTs can be opened by anyone with the link, and Knowledge files travel inside the GPT. If you need a Project-like artifact for a cross-org reviewer, package it as a Custom GPT:
Build Custom GPT → upload Project Files as Knowledge
→ Paste Project Instructions as GPT instructions
→ Share → "Anyone with link" → sendThis bypasses Project sharing limits at the cost of a small rebuild.
Step 7: If the share URL looks malformed, copy it raw
Slack / email clients sometimes break long URLs. Have the recipient:
Hover the link → "Copy link address" → paste into URL bar directly
→ Not click the rendered hyperlinkSome 404s are just truncated URLs from copy-paste.
How to confirm the fix
- Recipient opens the new link in incognito with the correct account and lands on the Project chat view.
- Recipient can read Project Instructions and at least one chat.
- For file-dependent flows, recipient confirms which files are visible vs which need separate attachment.
- Owner sees the new link in their Project’s Share history with a recent timestamp.
Common pitfalls
- Confusing chat share (
/share/...) with Project share — they are different links and serve different content. - Sharing a Team-workspace Project to a personal-account recipient and expecting it to work.
- Sending the link from a browser signed into a wrong workspace — the link is workspace-scoped.
- Assuming Files travel — they often do not; always confirm or attach separately.
- Not revoking old links when regenerating — multiple live links create confusion about which version is canonical.
FAQ
Q: Do Project share links expire? A: They can — admins on Team / Enterprise may set expiry. Always test the link in incognito immediately after generating.
Q: Can someone outside my org view my Project? A: Usually no. Cross-org Project sharing is restricted on most plans. Use Custom GPT or export the files.
Q: Will the recipient see my Project’s chat history? A: Depends on share mode. “Share Project” typically exposes Instructions and the specific chat you shared, not all chats in the Project.
Q: Can I share a Project read-only? A: Yes — most share modes default to read-only. Confirm in the Share modal before sending.
Q: Is there a way to share Files without making the recipient a workspace member? A: Not via Project Files directly. Use a Custom GPT (Knowledge travels) or a shared Drive folder.