[GH-ISSUE #978] Add 'everyone'-like user for all authenticated users #687

Open
opened 2026-05-07 00:26:35 +02:00 by BreizhHardware · 2 comments

Originally created by @gardient on GitHub (Dec 12, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/978

💡 Idea
Have an everyone-like special user for all authenticated users in the ACL.
something like all_authenticated/*auth

This would allow those self-host to set a basic/default set of ACLs for "registered" users

for example it would be excelent to set something like the UnifiedPush topics to be readable only by people who are authenticated

ntfy access '*auth' 'up*' ro

💻 Target components

ntfy server

Originally created by @gardient on GitHub (Dec 12, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/978 <!-- Before you submit, consider asking on Discord/Matrix instead. You'll usually get an answer sooner, and there are more people there to help! - Discord: https://discord.gg/cT7ECsZj9w - Matrix: https://matrix.to/#/#ntfy:matrix.org / https://matrix.to/#/#ntfy-space:matrix.org --> :bulb: **Idea** Have an `everyone`-like special user for all authenticated users in the ACL. something like `all_authenticated`/`*auth` This would allow those self-host to set a basic/default set of ACLs for "registered" users for example it would be excelent to set something like the UnifiedPush topics to be readable only by people who are authenticated ``` ntfy access '*auth' 'up*' ro ``` :computer: **Target components** <!-- Where should this feature/enhancement be added? --> <!-- e.g. ntfy server, Android app, iOS app, web app --> ntfy server
Author
Owner

@hansblaauw64 commented on GitHub (Jan 2, 2024):

Yeah, that would be great. Normal topics created by a validated user should be set read only for other users. Makes much more sense to me.

<!-- gh-comment-id:1874477607 --> @hansblaauw64 commented on GitHub (Jan 2, 2024): Yeah, that would be great. Normal topics created by a validated user should be set read only for other users. Makes much more sense to me.
Author
Owner

@kjetilho commented on GitHub (May 7, 2025):

I think this makes most sense for self-hosted. And in that case, a simple switch, "require authentication" would be a lot simpler to implement than to extend the semantics of the Permission type, and still solve 99% of the use-cases.

And happily, this is available: auth-default-access deny-all will require authentication for all operations. It can also be set to write-only to allow anonymous publication (spamming 😀 )

<!-- gh-comment-id:2860608937 --> @kjetilho commented on GitHub (May 7, 2025): I think this makes most sense for self-hosted. And in that case, a simple switch, "require authentication" would be a lot simpler to implement than to extend the semantics of the Permission type, and still solve 99% of the use-cases. And happily, this is available: `auth-default-access deny-all` will require authentication for all operations. It can also be set to `write-only` to allow anonymous publication (spamming 😀 )
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#687
No description provided.