-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow users to create ereaders #3531
base: master
Are you sure you want to change the base?
Allow users to create ereaders #3531
Conversation
@@ -456,6 +456,7 @@ | |||
"LabelPermissionsAccessAllLibraries": "Can Access All Libraries", | |||
"LabelPermissionsAccessAllTags": "Can Access All Tags", | |||
"LabelPermissionsAccessExplicitContent": "Can Access Explicit Content", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please only edit the en-us.json
file for the strings? We use Weblate to manage strings in all of the other translation files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, no problem. Wasn't sure how that worked.
Allow users to create ereaders
This is an enhancement feature that should close issue #1982 when merged. The purpose is to allow self-serve of the ereader devices by users of an Audiobookshelf instance. Personally, I'd much rather pass on the handling of ereader devices to the users themselves. Since it's disabled by default, it won't have any effect on current instances and only those who would like to utilize the feature can now have the opportunity to.
What's Changed
Client
Server
createEreader
permission for users with default false except for admin / root/api/me/ereader-devices
Screenshots
User account page with createEreader permission
Admin users page with new toggle