<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Colabrativ, Inc. &#187; Permission System</title>
	<atom:link href="http://www.colabrativ.com/tag/permission-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.colabrativ.com</link>
	<description>An Experiment Documentation and Electronic Notebook Provider</description>
	<lastBuildDate>Tue, 28 Oct 2014 04:44:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Upgraded Permission System in Clinical Entry and Operations, Version 3</title>
		<link>http://www.colabrativ.com/permission-system-in-cleo-version-3/</link>
		<comments>http://www.colabrativ.com/permission-system-in-cleo-version-3/#comments</comments>
		<pubDate>Wed, 22 Jan 2014 16:08:03 +0000</pubDate>
		<dc:creator>Marc Whitlow</dc:creator>
				<category><![CDATA[Announcement]]></category>
		<category><![CDATA[Cleo]]></category>
		<category><![CDATA[Permission System]]></category>

		<guid isPermaLink="false">http://www.colabrativ.com/?p=838</guid>
		<description><![CDATA[Colabrativ, Inc. is pleased to announce that its Clinical Entry and Operations (Cleo), Version 3 has been released with a new permission system. The new permission system gives the Cleo administrator finer control of what staff members can and cannot &#8230; <a href="http://www.colabrativ.com/permission-system-in-cleo-version-3/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Colabrativ, Inc. is pleased to announce that its Clinical Entry and Operations (Cleo), Version 3 has been released with a new permission system.  The new permission system gives the Cleo administrator finer control of what staff members can and cannot access in the Cleo suite of applications.  The new system replaces <a href="http://tomcat.apache.org/tomcat-7.0-doc/manager-howto.html#Configuring_Manager_Application_Access" target="_blank">Tomcat&#8217;s Application Access</a> that was used in Cleo versions 1 and 2.</p>
<h3>Permission System Advantages</h3>
<p>The integration of the new permission system into Cleo allows us to:</p>
<ol>
<li>Know who is logged into the application. </li>
<li>Know what requests users have made to the application, and provides a log of those requests.</li>
<li>Check that staff members have permission to view, add, change and/or update information in the database.</li>
<li>Create permissions that meet the needs of the organization using Cleo.</li>
</ol>
<h3>Permission System Roll-out</h3>
<p>The permission system is being rolled out in phases.  </p>
<ul>
<li>The first phase involved implementing the permission system in the administrative application admin, implementing the creation and control of staff member accounts and their permissions, and creating a reset password application to allow users to reset their passwords. </li>
<li>In the second phase, the permission system was implemented in the Explore application. Each request by a staff member is checked by the permission system. </li>
<li>In the third phase, the permission system will be implemented in the Operations application.  Finer control of staff member permissions will be available to Cleo&#8217;s administrators. </li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.colabrativ.com/permission-system-in-cleo-version-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
