Bug 7017 - override_renewals permission confusing
Summary: override_renewals permission confusing
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Kyle M Hall
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-12 19:55 UTC by Nicole C. Engard
Modified: 2016-01-26 22:30 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2011-10-12 19:55:38 UTC
You can set it so that a patron only has override renewals permission, but they can't access the circ module to override the renewals in the first place. I think we need to make it clear which permissions are dependent on other permissions.  Having a permission nested does not make that clear because in the example of the tools permissions you can pick and choose which ones you want to provide.
Comment 1 Marc Véron 2016-01-05 14:20:30 UTC
As far as I understand it, overdues_report, force_checkout, manage_restrictions work only if circulate_remaining_permissions is set. (Hmm, what about self_checkout?)

Maybe we could re-word the descriptions to make it clear? 

Something like:

[] circulate_remaining_permissions Basic circulation permissions

[] overdues_report Execute overdue items report (needs basic permissions)

[] force_checkout Force checkout if a limitation exists (needs basic permissions)

[] manage_restrictions Manage restrictions for accounts (needs basic permissions)

[] override_renewals Override blocked renewals (needs basic permissions)
Comment 2 Nicole C. Engard 2016-01-26 22:30:45 UTC
I wouldn't say 'basic' I'd say 'circulate_remaining_permissions' since that's what the permission is but that works.

Nicole