Elsevier |MC Strategies 2009 Administrator Roundtable Administrative Permissions & Update on Design Work March 19, 2009

. Administrative Levels Available Administrative Permissions Permission Discussion – what works/what doesn’t Update on Q1 New Feature Design Work

. System Administrator – Primary Organization Administrator Facility Administrator – Primary Administrator for the Facility Department Administrator Reports only Administrator – individuals in many areas Events Manager Administrator - Education Office On Track Administrator – Education Office Manager Zone – Managers with staff across Departments

System Administrator Privileges Overall access to all facilities, all departments, and all learners System administrators have permissions inclusive of any individual administrator, plus some unique permissions: Configure System Options Organization Wide Announcements Manually Mark Learner Lessons Complete Add Items to On Track Add CEs to an Event Change Learner Facility Use Administrator Reports Use Rules Manager View Course & Lesson Listing Look up other System Administrators View learner Passwords

Facility Administrator View all learners in the facility View Reports for all departments in the facility Access across the facility for any additional granted permissions Department Administrator View Department Reports View all learners in the department Access across the department for additional granted permissions

Report Level Administrator View Reports for all departments where access is granted View learners in those areas to access transcripts only Classes & Events Administrator Create and Schedule Events Enroll Learners across the Organization in events Update Waitlists Print Rosters – Labels View Classes & Events Reports for learners across the Organization

On Track Administrator Enroll Learners Mark Learners Complete Run On Track Reports Manager Zone Administrator Manage Training Create and Assign Modules Enroll Learners in Events Monitor Completion Rates Run Reports

Philosophy behind current permissions: Admins are given a scope (system, facility, department) along with permissions Checkbox permissions to avoid designating security roles in the system Define scope/permissions to meet organizational need Allow Managers to manage and meet organizational goals Modular to accommodate new permissions with new functionality as it is added More intuitive tabular review of permissions Every admin should be able to review reports of activity within their scope

Current Customer Requests for Permission Changes (original updated with items discussed in today’s session that will be carried forward for review/enhancements) Restrict visibility for Event Admins to only events they created – no discussion in favor Admin with permissions for all departments should automatically get permission over any new department that is made available – overall consensus - yes Keep edit module and assign module as separate privileges – within their scope? or across the instance? – no opinions Manager Zone - limit ability to remove lessons assigned by others – not much opinion Manager Zone – allow them read only access – consensus - yes

Current Customer Requests for Permission Changes (original updated with items discussed in today’s session that will be carried forward for review/enhancements) Allow Modules to be made Global for a facility only – consensus - yes Create facility level Sys Admin privileges - discussion agreed more options necessary, but not necessarily this way Expand scope for announcement permissions – consensus is to have multiple options. Keep current scope, but allow extension if necessary

Current Customer Requests for Permission Changes Allow an admin to have certain permissions across all facilities - consensus is to have multiple options. Keep current scope, but allow extension if necessary General discussion: Allow options to accept scope/permissions that are system default, or set custom permissions for a particular admin or group of admins Manager Zone gives too much functionality – need read only access to let them look at reports.. And allow manager zone to give reporting access to a selected group of individuals or their dept staff Need a report of admins that have all depts, and list the date for which they were granted access to that dept (even if added by rules manager) Allow Admins assigned to All Depts to automatically have permissions for any new Depts – overwhelming consensus-yes

What Works Like the opportunity to have many options The permissions list is easy to use Facility & Department Scope is working Available Permissions are working

What Doesn’t Work Manager Zone - be able to set parameters inc Reports only When new departments are added via download but Admins with Scope for all departments are not automatically updated Some Sys Admin Only reports need to be available to additional Admins Allow them to hand pick which of these they want an administrator to see Add All facility Option with the automated updates

Questions? Should an admin be allowed different permissions within different elements of their scope? So an admin could have one set of permissions for one department and a different set of permissions for another department? – no discussion Would you want to administer role based security? need to keep the options open.. Maybe allow the role-based security to be added in addition to the standard set of admin permissions. Allow the role to expand scope and permissions. But must create a role to override the scope. Open up the permissions with many options Are facility and department parameters sufficient for scope? General consensus - yes

Next Steps with Permissions MCS will evaluate feedback during this session MCS will identify administrative permission changes that need to be made Will review design with customer team for consensus. Changes will be scheduled in next available build Results of analysis will be reviewed at next admin roundtable

Collaborative Learning Design The design team is now iterating through a prototype of the new functionality. We are on target to complete the design by the end of March. Prototype design will be presented at next Admin Roundtable Report Manager Design Team – now accepting participants This design team is now being assembled. WebEx sessions will begin sometime during the last week of March or first week of April. This team will most definitely require 8 weeks of participation, 2-4 hours a week. If you are interested, please contact Peggy Simpson at Transcript Reporter Enhancements Design will begin mid-April Add/Edit Programs – New UI design Prototype design will be presented at next Admin Roundtable

Next Admin Roundtable – April 16, 2009 New feature prototype reviews Collaborative Learning Program Management – new UI to add/edit programs Focus for Admin Roundtable Discussions – May and June Getting more from your Learning Program – best practice case studies Industry Trends