[Archivesspace_Users_Group] Permissions per repository

[Callahan, Maureen]

Yeah, we decided that we really hated the out-of-the-box group settings, so we created groups based on permissions. Most users then belong to several groups. This way, no one has unnecessary permissions because they belong to a particular group. I have more details below my signature for anyone interested.

Maureen

Permission groups and roles

Manage a repository (manage locations, user groups, department codes, user access)
repository-managers
X manage this repository (change groups and other settings)

Transfer the entire contents of a repository
transfer-contents
X transfer the entire contents of a repository

Transfer distinct records across a repository
transfer-distinct-records
X transfer major record types between repositories

Create, read, and update accessions and top containers
create-accessions
X create/update accessions in this repository
X view the records in this repository
X create/update top container records

Create, read and update resources and top containers
create-resources
X create/update resources in this repository
X view the records in this repository
X create/update top container records

Create, read and update digital objects
create-digital-objects
X create/update digital objects in this repository
X view the records in this repository

Create, read and update event records
create-events
X create/update event records in this repository
X view the records in this repository

Create, update and delete container profile records  (affects all repositories)
container-profiles
X create/update/delete container profile records

Suppress records from this repository
suppress-records
X suppress the major record types in this repository
X view suppressed records in this repository

Delete records from this repository
delete-records
X delete event records in this repository
X delete the major record types in this repository
X delete/bulk update top container records

Delete or bulk update top containers in this repository
manage-top-containers
X  delete/bulk update top container records

Merge records from this repository
merge-records
X merge the major record types in this repository

View suppressed records in this repository
view-suppressed-records
X view suppressed records in this repository

View (non-suppressed) records in this repository
view-records
X view the records in this repository

Initiate and cancel an import job
import-jobs
X initiate import jobs
X cancel an import job

Create, merge, update and delete subject or agent records (affects all repositories)
subject-agent
X create/update/delete subject records
X create/update/delete agent records
X merge agent/subject records

Create, update and delete vocabulary or classification terms (affects all repositories)
vocabulary-classification
X create/update classifications and classification terms
X delete classifications and classification terms
X create/update/delete vocabulary records



On Dec 17, 2015, at 11:34 AM, Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>> wrote:

Thanks Kevin. I need to dig into the documentation again it looks like. I need to understand what each “group” has rights too.

Thanks again,

Phil


Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>
504-865-5607



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>[mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, December 17, 2015 10:31 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Permissions per repository

Hi Phil,

You can set these under “Manage User Access” in the repository settings, once you’ve selected the repository you want at the top of the page on the staff interface. We do this at Denver with the separate repository we use for LIS classes so that students can’t make any changes in the production repository.  -k

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suda, Phillip J
Sent: Thursday, December 17, 2015 9:28 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Permissions per repository

Greetings all,

                 Is there a way to set permissions per repository in staff interface? We have multiple repositories from multiple libraries across campus in one instance of ArchivesSpace. Staff from one library would prefer if users from another library (separate repository) were not able to see their accession data, etc.

Is there granularity in permissions that I am missing or is it sysadmin privileges or nothing?

Thanks,

Phil

Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>
504-865-5607

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=KjBjy1ui3-vwPLfgSWDRcC5eaC402Q5QqVkf_FYhcKE&s=6DZTokpj7DZ20OjzOrAbgMeQVUFLYMX7LNtLZKHm5X8&e=

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151217/82c6c110/attachment.html>