Add browse frontend auth: users table, login/logout, is_public filtering #26
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-api#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan
plan-2026-02-25-private-notes-auth— Phase 1User Story
As a platform owner
I need private notes hidden from unauthenticated browse visitors
So that sensitive internal docs (plans, issues, SOPs) are not publicly visible
Acceptance Criteria
When I visit /browse/ without logging in
Then I only see notes where is_public=True
When I log in via /browse/login with valid credentials
Then I see all notes (public and private) with a visual indicator on private ones
When I visit /browse/notes/{private-slug} without logging in
Then I get a 404 response
When I log out via /browse/logout
Then my session is cleared and I only see public notes again
Additional Information
Checklist
Related
pal-e-docs— project affected