Make only one page public of an authenticated site #4411

New Issue

OVERLORD · 2026-02-05T08:49:51+03:00

OVERLORD commented

2026-02-05 08:49:51 +03:00

Originally created by @stanislas14 on GitHub (Jan 17, 2024).

Attempted Debugging

I have read the debugging page

Searched GitHub Issues

I have searched GitHub for the issue.

Describe the Scenario

Hi,

My site is authenticated with LDAP authentication. The configuration is done in the .env configuration file and it works very well.

But I need a page on this site to be publicly accessible without authentication, is this feasible? I've played with permissions but I think authentication takes over every time.

Is there a solution? I would like to avoid making the site public and putting permissions on each shelf..

Regards

Exact BookStack Version

v23.12

Log Content

No response

Hosting Environment

PHP 8.1 on redhat 9

Originally created by @stanislas14 on GitHub (Jan 17, 2024). ### Attempted Debugging - [X] I have read the debugging page ### Searched GitHub Issues - [X] I have searched GitHub for the issue. ### Describe the Scenario Hi, My site is authenticated with LDAP authentication. The configuration is done in the .env configuration file and it works very well. But I need a page on this site to be publicly accessible without authentication, is this feasible? I've played with permissions but I think authentication takes over every time. Is there a solution? I would like to avoid making the site public and putting permissions on each shelf.. Regards ### Exact BookStack Version v23.12 ### Log Content _No response_ ### Hosting Environment PHP 8.1 on redhat 9

OVERLORD added the 🐕 Support label 2026-02-05 08:49:51 +03:00

OVERLORD closed this issue

2026-02-05 08:49:51 +03:00

OVERLORD commented

2026-02-05 08:49:54 +03:00

@ssddanbrown commented on GitHub (Jan 17, 2024):

Hi @stanislas14,
The main way to do this is to make the site public, but alter the guest role permissions so it has no permissions by default, then assign view permissions as required per book/chapter/page.
Note though, this does take away a significant layer of defence to the site.

Alternatively, if you have development skills, you could use the REST API to fetch your page content then display externally, or build some level of automation using the tools we provide (webooks, theme systems).

@ssddanbrown commented on GitHub (Jan 17, 2024): Hi @stanislas14, The main way to do this is to make the site public, but alter the guest role permissions so it has no permissions by default, then assign view permissions as required per book/chapter/page. Note though, this does take away a significant layer of defence to the site. Alternatively, if you have development skills, you could use the REST API to fetch your page content then display externally, or build some level of automation using the tools we provide (webooks, theme systems).

OVERLORD commented

2026-02-05 08:49:57 +03:00

@stanislas14 commented on GitHub (Jan 22, 2024):

Hi,

Thanks a lot for your answer. Indeed, we have to look at the problem in reverse. This solution works

regards

@stanislas14 commented on GitHub (Jan 22, 2024): Hi, Thanks a lot for your answer. Indeed, we have to look at the problem in reverse. This solution works regards

OVERLORD commented

2026-02-05 08:49:59 +03:00

@ssddanbrown commented on GitHub (Jan 22, 2024):

Good to her that works.
I'll therefore close this off.

@ssddanbrown commented on GitHub (Jan 22, 2024): Good to her that works. I'll therefore close this off.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#4411