Content update

README.md

@@ -22,6 +22,7 @@ Time | Section | Description
 00:00 | 1. [Identity Registries](/episodes/identityRegistries.md) | COmanage is an Identity Registry. Why do these exist?
 00:10 | 2. [What is COmanage?](/episodes/whyCOmanage.md) | What does COmanage do & who uses it?
 00:25 | 3. [Focus on Capabilities](/episodes/capabilities.md) | What capabilities should you consider for your registry?
+00:00 | 4. [The structure of COmanage](/episodes/structure.md) | How is COmanaged structured?
 
 _The actual schedule may vary slightly depending on the topics and exercises chosen by the instructor._
 

episodes/identityRegistries.md → episodes/01-identityRegistries.md

@@ -37,3 +37,23 @@ We'll talk about capabilities later... key tools:
 * IBM Tivoli Identity Manager
 * Oracle Identity Manager
 * ForgeRock Identity Platform
+
+---
+
+## Some review: What is COmanage again?
+
+COmanage is a Membership Management Service. These tools provide many things:
+
+* An interface for user enrollment
+* The ability to assign rights and permissions to people through roles, groups, etc
+* The ability to distribute the management of rights and permissions to multiple people. _For example, a project's Principal Investigator can manage the rights and permissions for his/her project group_
+
+COmanage is not the only Membership Management Service. Examples of other services include
+
+* HEXXA
+* PERUN
+* <others... should have a more complete list>
+
+Some will have strong preferences of one tool over another, though at their core, each of these tools serve the same basic functions. Their differences are primarily in the emphasis each tool makes on various features, how the development of the tool is managed, and how the tool is packaged with other tools.
+
+Since you are here, we are assuming that you have already made the choice to use COmanage.

episodes/whyCOmanage.md → episodes/02-whyCOmanage.md

@@ -14,6 +14,8 @@ Where does the Registry sit in an Identity and Access Management (IAM) architect
 
 ## What COmanage does
 
+COmanage Registry combines group management with configurable and flexible enrollment workflows to support the quick and easy spin up of collaborations focusing on a common task or goal.
+
 COmanage is a key tool for several things: 
 
 * Enrolling individuals into your Identity and Access Management systems in diverse ways

episodes/04-structure.md

@@ -0,0 +1,62 @@
+---
+title: "The structure of COmanage"
+teaching: 15
+exercises: 0
+questions:
+- "Question here"
+objectives:
+- "List the objectives"
+keypoints:
+- "List the key takeaways for the episode"
+---
+
+How is COmanaged structured?
+
+# Platform - Organizations/ Collaborations - sub-units
+
+## The platform
+
+There are several platform settings. Some of these are managed within the COmanage CO.
+
+The COmanage CO is created automatically for all new deployments, as the "meta" CO used to manage the platform itself. While the COmanage CO operates the same way as any other CO, it does have various special characteristics:
+
+1. Anyone in the `CO:admins` group within the COmanage CO is considered a [Platform Administrator](https://spaces.at.internet2.edu/display/COmanage/Registry+Administrators).
+2. Similarly, [API Users](https://spaces.at.internet2.edu/display/COmanage/REST+API+v1) created within the COmanage CO are given full access to the platform.
+3. [CO Themes](https://spaces.at.internet2.edu/display/COmanage/Modifying+the+UI+Look+and+Feel) created in the COmanage CO will apply globally, unless overridden by another CO's Theme.
+
+## Collaborative Organizations (COs)
+
+
+## CO sub-units
+
+## Collaborative Organization Units (COUs)
+
+COUs are structural Objects
+
+## Collaborative Organization Departments (CO Departments)
+
+CO Departments are Primary Registry Objects
+
+## Collaborative Organization Groups (CO Groups)
+
+CO Groups are Primary Registry Objects.
+
+
+# People
+
+## Org Identity
+
+
+
+## COPerson
+
+
+
+## Roles
+
+
+
+## Efficiency Capabilities
+
+... API, Bulk operations, Search
+