Feature #4132
No way to restrict groups or individual users with log-in privileges to access accessions, manage accessions, donors and rights.
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Medium | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Sponsored: | No | Tested version: |
Description
Google user: jessica%...@gtempaccount.com
To reproduce this error:
========================
1)Add user to any group.
Resulting error:
================
After log-in can access Add menu and Manage menu.
Expected result:
================
There should be a way of limiting access to accessions module in a similar way to permissions for authority records, archival descriptions, functions and specific repositories.
[g] Legacy categories: Access control, User management
Related issues
History
#1 Updated by David Juhasz over 10 years ago
I don't think we can currently set user permissions on functions or authority records, can we?
#2 Updated by David Juhasz over 10 years ago
I'd classify this as an enhancement. It's a lot of work and it wasn't part of the original accession module requirements, as far as I know.
[g] Labels added: Type-Enhancement
[g] Labels removed: Type-Defect
#3 Updated by Anonymous over 10 years ago
In ICA-AtoM we can control permissions to create or update authority records and create, update, and delete subject terms (taxonomies). Sorry not functions.
#4 Updated by David Juhasz over 10 years ago
- Target version changed from Release 1.2.1 to Release 1.3
[g] Labels added: Milestone-Release-1.3
[g] Labels removed: Milestone-Release-1.2.1
#5 Updated by Anonymous about 10 years ago
- Target version changed from Release 1.3 to Release 2.1.0
[g] Labels added: Milestone-Release-2.0
[g] Labels removed: Milestone-Release-1.3
#6 Updated by David Juhasz almost 10 years ago
Reassign to new account.
[g] New owner: David Juhasz
#7 Updated by David Juhasz over 9 years ago
- Priority changed from High to Medium
- Target version deleted (
Release 2.1.0) - Sponsored set to No
No funding for feature, removing from 2.0 roadmap.
#8 Updated by Dan Gillean almost 7 years ago
- Project changed from Access to Memory (AtoM) to AtoM Wishlist
Moved to AtoM wishlist until sponsored for inclusion.
#9 Updated by David Juhasz almost 6 years ago
- Assignee deleted (
David Juhasz)