Hierarchy, Tree View, and Permissions

<p>We've been working on a big new feature set: improved handling of different levels of hierarchy and permissions in the admin site. The first release, pushed out a day or two ago, provides a couple of important enhancements over the existing method, first explained by Eric in <a href="http://libraryh3lp.blogspot.com/2008/05/hierarchy.html">May of last year</a>.<br /><br />To rundown the changes:<br /><br /><span style="font-weight: bold;">Tree View</span>, found in the users/queues area, gives the admin a graphical display of their system's hierarchy. Admins can see what users own what queues, and they can assign users as owners of queues. Drag and drop works, too. You can switch back to the default display by clicking Flat View.<br /><br /><span style="font-weight: bold;">Has Admin Rights</span> is a checkbox that will appear when a user is selected. Ticking that checkbox will give the selected user admin rights at the same permissions level as his or her "boss" one level up in the hierarchy.<br /><br />Why would you want to do this? Let's say you work at a large university, with several libraries. You have a top-level account called <span style="font-style: italic;">big-admin</span><span style="font-weight: bold;"> </span>registered with LibraryH3lp. <span style="font-style: italic;">Big-admin</span> can create users to act as admins of their own individual libraries at the university: <span style="font-style: italic;">main-library-admin</span>, <span style="font-style: italic;">law-library-admin</span>, <span style="font-style: italic;">health-library-admin</span>, etc... <span style="font-style: italic;">Big-admin</span> can create and assign queues to those mini-admins using Tree View, or the lower-level admins can create their own queues independently.<br /><br />When <span style="font-style: italic;">law-library-admin</span> logs into the admin site, they will only see queues that they themselves own, and they can create their own users to assign to their queues. They may also wish to share the task of running the chat system in the Law Library by assigning admin rights to one of their own users. This will grant that user the same permissions that they themselves have.<br /><br />This is also a good way to build a collaborative service spanning multiple institutions. If you have existing top-level admin sites that you'd like to put together, let us know, and we can do that manually.<br /><br />All of this can cascade through as many levels as you wish. As has always been the case, <span style="font-weight: bold;">ALL</span> operators <span style="font-weight: bold;">anywhere </span>in the hierarchy can transfer chats and IMs on queues to any other queue or operator within the same administrative domain (starting from the top-most level).<br /><br /><span style="font-weight: bold;">Things still to come: </span><br /><ul><li>Read-only access to reports and transcripts for ALL users on the queues to which they are assigned.</li><li>Write access to the transcripts/Monitor Activity area for "mini-admins" granted rights with the "has admin rights" function.<br /></li><li>Way for top-level admins to connect with other top-level admins in order to merge admin domains with no intervention from us.<br /></li></ul></p>

We've been working on a big new feature set: improved handling of different levels of hierarchy and permissions in the admin site. The first release, pushed out a day or two ago, provides a couple of important enhancements over the existing method, …