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. Since the October 2025 sharing redesign (now on Free, Plus, Pro, Business, Enterprise, and Edu), a Project is shared through an in-app Share pane where you invite specific people and set their role — it is not a public token URL like a shared chat. So a 404 almost always means one of three things: the recipient was never actually invited, they opened it while signed into the wrong account, or you set the link to Only those invited instead of Anyone with the link.
Fastest fix (resolves most cases): open the Project → Share (top right) → confirm the recipient’s exact email is listed with Can chat access → if not, add it → tell them to open the link in incognito and sign in with that exact email. If you need link-based access, switch the pane from Only those invited to Anyone at <org> with the link (Business/Enterprise) or invite by email (personal plans).
Common causes
Ordered by hit rate, highest first.
1. The recipient was never added to the Share pane
This is now the number-one 404. Project sharing is invite-scoped: the person’s account has to appear in the Project’s Share list (or the link has to be set to Anyone with the link). Forwarding the raw URL to someone who isn’t on the list gives them 404 or “You do not have permission,” even inside the same workspace.
How to spot it: open the Project → Share. If the recipient’s email is not in the member list and the link mode is Only those invited, that is your cause.
2. Recipient is signed into the wrong ChatGPT account
They have a personal account and a work account, and the browser auto-signed them into the one you did not invite. The invite is tied to a specific email address, so the wrong account fails the permission check.
How to spot it: recipient opens the link in incognito, signs in with the exact email you invited, and it works.
3. Personal-account Project shared, but recipient expected workspace behavior (or vice-versa)
Sharing semantics differ by plan. On Business / Enterprise / Edu, a Project can be shared with workspace members only — you cannot invite an outside email, and a workspace link will 404 for anyone outside the org. On Free / Plus / Pro personal accounts (sharing added Oct 2025), you invite people by email and they join with Can chat by default; there is no org boundary, but the person still must be invited.
How to spot it: owner is on a Business/Enterprise workspace and the recipient is a personal account outside the org — that combination cannot be shared link-to-link; the recipient must be a workspace member.
4. The 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. A shared chat URL contains /share/ (or /c/ for a private chat that 404s for others) — it shows one conversation, not the Project’s files and instructions.
How to spot it: the URL contains /share/ or /c/. A real Project link is opened from the Project’s Share pane, not from a chat’s share button.
5. Sharing was disabled at the workspace level
Business / Enterprise admins can disable sharing or restrict it to internal-only. The Share button may still appear, but invites outside the allowed scope 404.
How to spot it: admin confirms sharing is restricted, or the Share pane hides the Anyone with the link option.
6. Recipient’s access was revoked, or the link mode was changed
If you removed the person from the Share pane, or flipped the link from Anyone with the link back to Only those invited, anyone relying on the old link now gets 404. Deleting and regenerating a shared chat link has the same effect — old viewers lose access immediately.
How to spot it: it worked yesterday and 404s today, and you (or an admin) edited sharing in between.
Which bucket are you in
| Symptom the recipient reports | Most likely cause | Jump to |
|---|---|---|
| 404 / “no permission”, their email not in Share pane | Not invited (cause 1) | Step 2 |
| Sees a sign-in screen, then 404 | Wrong account (cause 2) | Step 1 |
| Outside-org person, owner on Business/Enterprise | Workspace-only sharing (cause 3) | Step 3 |
Link has /share/ or /c/ in it | Chat link, not Project (cause 4) | Step 4 |
| ”Share” works internally but never externally | Admin policy (cause 5) | Step 5 |
| Worked before, 404s now | Access revoked / mode changed (cause 6) | Step 2 |
Before you start
- Confirm your plan (Free / Plus / Pro vs. Business / Enterprise / Edu) — sharing rules differ.
- Confirm whether you and the recipient are in the same workspace, or separate accounts entirely.
- Have the recipient send a screenshot of the exact error page with the URL bar visible.
- Open the Project’s Share pane yourself so you can see who is currently listed.
Info to collect
- Full share URL (mask any token if posting publicly).
- Owner plan + workspace; recipient plan + account email.
- Screenshot from the recipient side, URL bar visible.
- Whether you used the Project’s Share pane or a chat’s “Share” button — confirm exactly.
- The link mode currently set:
Only those invitedvsAnyone with the link.
Shortest fix path
Ordered by ROI. Steps 1 and 2 resolve most cases.
Step 1: Confirm the recipient is signed into the invited account
Tell the recipient:
1. Open the share link in a NEW incognito / private window.
2. When prompted, sign in with the exact email I invited
(the work email, not a personal one).
3. If a workspace switcher appears, choose the same workspace as mine.
4. Reload the link.This resolves the largest share of “404 on first click” cases, because the invite is bound to one email address.
Step 2: Open the Share pane and confirm the recipient is listed
Owner side:
Open Project → Share (top-right) → check the member list
→ Recipient's exact email present? If not, add it:
type their email → set role (Can chat / Can edit) → Invite
→ Both of you get an email confirming the invite
→ Have them open the link again, signed into that emailIf you would rather not invite person by person, switch the link mode in the same pane:
Share pane → change "Only those invited" to
• "Anyone at <your org> with the link" (Business / Enterprise)
• or invite by email (Free / Plus / Pro)
→ Copy the fresh link and resendCan chat lets them create chats and view files/instructions; Can edit also lets them change instructions and add or remove files. Workspace-link joiners default to Can chat — you can upgrade them to Can edit afterward from the same pane.
Step 3: For cross-org reviewers, add them to the workspace
On Business / Enterprise / Edu, Projects share with workspace members only — there is no outside-email invite. If the reviewer is external:
Settings → Workspace → Members → Invite
→ Enter their email → assign a seat/role
→ Wait for them to accept (check spam folder)
→ Then add them in the Project's Share paneIf adding a seat is not an option, fall back to exporting (Step 6) or, for read-only handoff, package the artifact as a Custom GPT (Step 7).
Step 4: Make sure it is a Project link, not a chat link
Open the Project (not a single chat)
→ Share (top-right of the Project) → Copy link
→ Confirm the URL did NOT come from a chat's share buttonA chat link (/share/...) only shows one conversation. The Project link from the Share pane carries the Project’s files, instructions, and the chats your role can see.
Step 5: Check the workspace sharing policy
Business / Enterprise admin:
Admin Console → Workspace settings → Sharing
→ Confirm sharing (and "Anyone with the link", if you need it) is enabled
→ If disabled, either enable it or use an internal-only alternativeIf your admin keeps external sharing off for policy reasons, link sharing simply will not reach outsiders — switch to file export or a workspace seat.
Step 6: Export and re-attach files when sharing truly is not possible
For cross-org handoffs that policy blocks:
Project → Files → download the files → zip → send via Slack / email
→ Recipient: create their own Project, upload the files,
paste your Instructions textFor repeated handoffs, keep a shared Google Drive folder as the source of truth instead of relying on Project Files crossing org boundaries.
Step 7: Use a published Custom GPT for anyone-with-link reviewers
Custom GPTs (Plus and up) have public-link sharing and their Knowledge files travel inside the GPT. If you need a Project-like artifact for an outside reviewer who can’t be invited:
Build a Custom GPT → upload the Project Files as Knowledge
→ paste the Project Instructions as the GPT instructions
→ Share → "Anyone with a link" → sendThis trades a small rebuild for true link-based, cross-org access.
Step 8: If the URL looks malformed, copy it raw
Slack / email clients sometimes mangle long URLs.
Hover the link → "Copy link address" → paste into the URL bar directly
→ Do NOT click the rendered hyperlinkSome 404s are just a truncated URL from copy-paste.
How to confirm the fix
- The recipient’s email appears in the Project’s Share pane with a role (
Can chatorCan edit). - The recipient opens the link in incognito, signed into that exact email, and lands on the Project view (not a 404).
- They can read the Project Instructions and at least one chat; if they have
Can chat, the file panel is visible. - The owner sees the invite-confirmation email and the recipient listed as a member.
Common pitfalls
- Forwarding the raw URL instead of inviting the person in the Share pane — invite-scoped links 404 for anyone not on the list.
- Confusing a chat link (
/share/...) with a Project link — they serve different content. - Expecting a Business/Enterprise
workspace linkto work for someone outside the org — it will not; they must be a workspace member. - Flipping the link back to
Only those invitedafter sharing it widely, then wondering why old links 404. - Assuming files never travel — since the Oct 2025 redesign, invited members with project access DO see files and instructions; the old “files never travel” rule no longer holds.
FAQ
Q: Can someone outside my organization view my Project?
A: On Business / Enterprise / Edu, no — Projects share with workspace members only. On personal Free / Plus / Pro accounts, you can invite anyone by email (sharing added October 2025), but they still have to be invited or have an Anyone with the link mode enabled.
Q: Why does the link 404 even though we’re in the same workspace? A: Most likely the recipient was never added to the Project’s Share pane, or they’re signed into a different account than the one invited. Add their exact email and have them open it in incognito.
Q: Do files and instructions travel to people I share with? A: Yes. Since the October 2025 redesign, anyone you invite with project access sees the files, instructions, and the chats their role allows. This is different from the older behavior where files did not travel.
Q: What’s the difference between “Can chat” and “Can edit”?
A: Can chat lets a member create chats and view files and instructions. Can edit additionally lets them change instructions and add or remove files. Workspace-link joiners start at Can chat.
Q: It worked yesterday and 404s today — what changed?
A: Someone removed the recipient from the Share pane, switched the link from Anyone with the link back to Only those invited, or deleted and regenerated the link. Re-invite the person or re-share the current link.
Q: Do Project share links expire? A: They can — admins on Business / Enterprise may set expiry or revoke access, and deleting a shared link cuts off existing viewers immediately. Test the link in incognito right after generating it.