makeplane / makeplane/plane

[bug]: Guests can see Pages in project navigation but cannot discover/open public project pages without direct URL

Open
#9,103 1 comment 0 reactions 2 assignees View on GitHub

@anmolsinghbhatia is already working on this.

Since Aug 4, 2026.

🐛bug plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current behavior
Summary

Project guests see the Pages link in the project sidebar, but they cannot use it to discover or open pages that are marked Public. Public pages are accessible only if the direct URL is shared separately. This makes the Pages navigation misleading for guests.

Steps to reproduce
Environment

Plane Cloud
Project has Pages enabled
A page is set to Public
User is added to the project as Guest

Steps to reproduce

Enable Pages for a project.
Create a page in that project.
Set the page access to Public.
Add another user to the project with the Guest role.
Sign in as that guest.
Open the project.
Notice the Pages link is visible in the project sidebar.
Try to use that Pages area to find or open the public page.

Actual result

The guest sees a Pages link in the project navigation.
The guest cannot meaningfully browse project pages there.
The public page is not discoverable from the guest UI.
The page only works if the direct URL is shared out-of-band.

Expected result

One of these should happen:

Guests should be able to discover and open Public pages from the Pages area, or
The Pages navigation should be hidden for guests if it is not usable, or
The UI should clearly explain that guests can access only direct-link public pages.

Why this is a problem

The current behavior suggests access where there is no practical access path.
Seeing Pages in the sidebar implies that pages are available, but in reality the guest cannot use that navigation to reach public pages. This is confusing and creates support friction.

Impact

Confusing UX for guests
Extra manual work because page URLs must be sent separately
“Public” pages are accessible but not discoverable
Project navigation appears broken or misleading

Suggested fix

Show discoverable public pages in the guest-visible Pages area, or
Hide/disable the Pages nav for guests when they have no usable page access, or
Add a guest-friendly landing state that lists public pages available by direct access

Environment

Production

Browser

Google Chrome

Variant

Cloud

Version

Latest (thats all it says)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.