Summary: | Permissions for additional content - HTML Customizations, Pages, News, OPAC, etc | ||
---|---|---|---|
Product: | Koha | Reporter: | Sally Lodico <Slodico> |
Component: | Tools | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | dcook, jjayne |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35693 | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Sally Lodico
2024-09-05 17:08:27 UTC
(In reply to Sally Lodico from comment #0) > I suggest there be 2 new permissions that allow editing News items in the > staff interface. One permission would be to edit their own library's News > e.g. edit_own_news and the other to edit all News items e.g. edit_any_news. Historically, these types of permissions wouldn't really fit with how we do permissions/authorizations, but "view_borrower_infos_from_any_libraries" has set a precedent for these more complicated permissions. I suppose "edit_own_news" and "edit_any_news" would essentially be the same as "list_borrowers" and "view_borrower_infos_from_any_libraries", but with a better naming convention. Personally, I would think "edit_any_news" should be mutually exclusive with "edit_own_news" but we probably don't need to worry about that at this point. I look forward to seeing other comments, but I think this probably sounds all right. I think it implies a future direction that the permission model needs to go and that's taking into consideration more the "subject" and "object" of the action (ie verb). I'd like to see more granular permissions also. We would like to restrict some of those who can create News items to only be able to create their own and not be able to rearrange or edit the existing (shared) News items. Additionally, I think we should be able to restrict who has the ability to make HTML customizations. Right now, if we turn on the ability to edit & create News items, HTML customization gets turned on with it. |