Summary: | staffaccess permission requires borrowers permission | ||
---|---|---|---|
Product: | Koha | Reporter: | Nicole C. Engard <nengard> |
Component: | Patrons | Assignee: | Kyle M Hall <kyle.m.hall> |
Status: | ASSIGNED --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | dcook, gmcharlt, martin.renvoize, srdjan, veron, wizzyrea |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Nicole C. Engard
2011-10-03 17:33:23 UTC
So which one is preferred? I think the first option - it makes sense that you need borrower permission to be able to set staff permissions. So I say move the option for staffaccess up under borrowers so it's clear that you need borrowers permissions to access staff permissions. I'm up for other opinions of course. Move the permission under borrowers, please. That makes good sense. Still valid? I am not sure about moving it into the borrowers permission: staffaccess: Allow staff members to modify permissions for other staff members Could it make more sense to put it under permissions? Moving it is not only a visual change, but will also change how this permission is stored in the db as it will move from top to second level. Also: - People now having full borrowers will have to be changed to have all borrowers sub permissions but staffaccess. - People now having staffaccess need to get the new sub permission. Also: userflags has to be updated. I agree with Katrin. It's not feasible to turn "staffacess" into a subpermission of "borrowers". In theory, the "staffaccess" line could be moved up and placed adjacent to the "borrowers" and "permissions" lines. However, that would probably require a re-jigging of the templating, since right now the permissions are in "bit" order. That re-jigging might be a good idea though, as there are other permissions that could potentially be grouped together functionally. I suggest to just add a hint to the permission as an easy fix. (In reply to Katrin Fischer from comment #8) > I suggest to just add a hint to the permission as an easy fix. Makes sense to me |