As a systems administrator, I would like for the ability to create location records to be a distinct permission function option when creating user groups. Currently, a user must be in a group with the "manage this repository" function in order to create location records; other specific functions, like the ability to create/update/delete location profile records, are explicitly called out as separate permission functions. I have some staff members who need to create or update location records due to the work they perform, but I do not want them to have larger abilities to manage the repository records.
Screenshot with list of possible permission functions as of 2.5.2 is attached.
We here at the University of Amsterdam would also like the ability to create locations to be a distinct permission function instead of having to give the permission to manage repository records.
Thanks in advance!
University of Amsterdam
+1 from the Smithsonian. This presents a roadblock to using locations in the archivesspace.
We’ve also noticed that users can create locations from the new CSV import option, even though they can’t create in the staff interface, and can’t edit or delete the imported results.
Moving to development - Dev Pri