1 Welcome CMS V Workshop Employee Central.

2 Project Sequence – Training, Workshops, Hands-on Sessions Overall Governance -- Completed/Ongoing Portal II Communication Planning (CP)Communication Planning (CP) CP Workshop Create CP Strategy CP Action Planning CP Execution Taxon- omy I CMS IPortal I Governance Overview I Training & Workshop Activities Format Set-up Content Migration Pre-Launch Slides Interwise Live Mtg. CBT CBT CBT CMS IV CMS V Taxo III Hands-on Working Sessions Taxo II CMS III CMS II EC Over- view WS WS WS WS WS WS WS Delivery WS Solution Concept Content Inventory Preparation Project Timeline Kickoff Interwise and I-Learn Slide Decks Slide Decks

3 Agenda – CMS V: Folders, Metadata, & Security Criteria for New Folders Create New Folder Structure Security – Groups/ACLs

4 Criteria for New Folders Evaluate the following: –Obsolete organization of content –Too little content in some folders –Too much content in some folders –Content too tangled – need tidying, etc. With HalWorld, the folder structure organizing content tends to be archaic (inherited) due to a lack of folder “governance” – so moving to CMS provides an opportunity to clean up this folder structure Archaic/Chaotic vs. Logical Organization

5 Create New Folder Structure Creating the folder structure early is a must – and this requires a view into the future since changing the folder structure later can be a challenge A folder structure should be based on how you organize your content rather than on how you want to present content or how your department or workgroup is organized Sample Folder Structure as it appears in CMS – Web Desk Pro Sample Folder Structure created in Excel

6 Create New Folder Structure Key Steps/Questions: –Review HalWorld charter (folder structure) –How is content organized? (based on?) –How much content is there (per folder)? –What would you change? –Create a draft folder structure –Will the proposed structure last? (at least 12 months or longer)

7 Content-Level Security Content Security (restrictions) – Identifying access to content – restricted, confidential, internal use, public access. Security Definitions Access Control All information must be identified and classified according to its level of confidentiality and business need-to-know. Classifications are: PUBLIC, INTERNAL USE, CONFIDENTIAL, and RESTRICTED. Anyone requiring access to confidential or restricted information that is owned by another group must obtain permission from the Business Owner. Classification of the data is the responsibility of the Business Owner but can be delegated. Although not recommended to have multiple owners for the same data, this sometime occurs. Where there is more than one owner of the confidential data, Business Owners must designate a Business Owner who will make access decisions on behalf of all the owners of this data... Restricted High - Critical Value Information intended for restricted use only by those employees with an explicit, predetermined stringent business need-to-know. Information whose unauthorized disclosure or destruction would result in severe damage, provide significant advantage to a competitor, or cause penalties to HAL, its customers, or employees, and/or cause significant impact to HAL systems and business operation... Confidential High Risk (Medium - Critical Value) Information intended for sole use within HAL and limited to a need-to-know. Information whose unauthorized disclosure or destruction would directly or indirectly result in adverse impact on HAL, its customers, or employees. Financial loss, damage to HAL’s reputation, loss of business, and potential legal action could occur... Internal Use Moderate Risk (Low - High Value) Information is limited to HAL employees, contractors, and vendors covered by a non-disclosure agreement. If there is an unauthorized disclosure, compromise, or destruction of this information, there would be minimal or no significant impact to HAL, its customers, or employees. This is the default classification... Public Low Risk (None or Unclassified) Information that can be disclosed to anyone. It would not violate individual’s right to privacy. Knowledge of this information does not expose HAL to financial loss, embarrassment, compromise a competitive advantage or jeopardize the security of HAL.

8 Security – Groups/ACLs (access control lists) CMS has the ability to define content-level security/access – as in this sample table, which is also shows the methodology to follow to determine content-level security Content Name Description Purpose of the restriction CMS Users User(s) who will manage the content in CMS Portal Users Users who will have access to the content on the portal All Accounting UsersThis group will have access to the workgroup and unrestricted content Names RedBook UsersThis group will have access to the RedBook files; no other users should be able to view these files Names Exposure ReportCut editions to provide versioning Names

9 Thank You community pages only CMS V Employee Central. More Training: Portal Training and Policies Site