<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap:break-word"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Hi there Eric,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Access to the “Create” for containers is provided by the update_container_record<b> </b>role. It looks like this isn’t granted to managers (repository-managers) by default. This has a bug vibe and I’ll ensure a JIRA issue is recorded.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">In the meantime, you can expand the roles available to your repository managers by following these steps:</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">1. Login as an administrator</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">2. Ensure the repository you’d like to update is selected</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">3. Under the ‘cog’ icon next to the repository name, select "Manage Groups”</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">4. Select ‘Edit’ next to the repository-managers group</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">5. Under “Members can”, ensure the checkbox for "create/update top container records” is selected</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">6. Save Group</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Hopefully the “Create” action will now be available!</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Thanks,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Payten</div> <br> <div id="bloop_sign_1479279308637298176" class="bloop_sign"></div> <br><p class="airmail_on">On 16 November 2016 at 11:47:21 AM, Gadsby, Eric T. (<a href="mailto:egadsby@towson.edu">egadsby@towson.edu</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div style="word-wrap:break-word" class=""><div></div><div>
<title></title>
<div class="">I posted this to the list earlier but the list seems
more active this week so I thought I’d try again. One of ouse users
is manger of a collection but can’t create containers in it here is
what they report: </div>
<div class=""><br class=""></div>
<div class="">“While attempting to create top containers for
instances, I only had access to “browse” but not create. I had
management level access at the time. I had to be given admin level
access to be able to gain the create button for top containers. The
create option disappeared when placed on just admin level access. I
had to be placed in both levels of access to be able to create top
containers.” </div>
<div class=""><br class=""></div>
Our server has only been in production for a few weeks and is
set-up per the <a href="http://www.archivesspace.org" class="">http://www.archivesspace.org</a> recommendations. Our
server does authenticate via LDAP (Active Directory) but our users
experience is the same using an AD or ArchivesSpace local users. Do
you know how we might resolve this or what might be the next steps
in troubleshooting? Thanks! <br class="">
<br class="">
Sincerely,<br class="">
<br class="">
Eric T Gadsby<br class="">
IT Operations Specialist, Cook Library<br class="">
Towson University<br class="">
<a href="mailto:egadsby@towson.edu" class="">egadsby@towson.edu</a><br class="">
410-704-3340
_______________________________________________
<br>Archivesspace_Users_Group mailing list
<br><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a>
<br><a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a>
<br></div></div></span></blockquote></body></html>