diff --git a/_episodes/01-co.md b/_episodes/01-co.md index 6c64904..c717a9b 100644 --- a/_episodes/01-co.md +++ b/_episodes/01-co.md @@ -52,11 +52,11 @@ COmanage Registry defines several types of administrators. --- -# Hands on - The organization model +# Hands on - The organization model - COs ![Interactive system activity](/assets/img/hands-on-keyboard.png) -In this lesson you each will start to build an organizational model to serve as an example. Using the [Modeling Organization :memo:](/files/handouts/CO310-ModelingOrgs.pdf), write down a name for the `CO`:gear: you will be working with for the workshop. Consider the people that you outlined in the first lesson, and pick a `CO`:gear: to which these individuals would be belong (along with the person's memberships that you have outlined.) +In this lesson you each will start to build an organizational model to serve as an example. Using the [Modeling Organization :memo:](/files/handouts/CO320-ModelingOrgs.pdf), write down a name for the `CO`:gear: you will be working with for the workshop. Consider the people that you outlined in the first lesson, and pick a `CO`:gear: to which these individuals would be belong (along with the person's memberships that you have outlined.) [5 min] @@ -105,17 +105,17 @@ We will now implement what you have specified on your worksheets. 1. Using the credentials you specified as part of the COmanage setup, sign into the system. These credentials have Platform Administrator privileges which enable you to create `COs`:gear:. Once you sign in you will see a list of available collaborations. -## Create a `COs`:gear: +## Create a `CO`:gear: **REQUIRED ROLE**: `CMP Administrator`:crown: 2. From the menu, select Platform > COs to display the CO Management Overview List. -![Screen shot - Navigate to the CO Management Overview List](/fig/O310-01_COMgmtList_2019-09-06.png) +![Screen shot - Navigate to the CO Management Overview List](/fig/O320-01_COMgmtList_2019-09-06.png) 3. Click the "Add CO" link above the table on the right side to add a new `CO`:gear:. -![Screen shot - CO Management Overview List](/fig/CO310-01_COMgmtOverviewList_2019-09-06.png) +![Screen shot - CO Management Overview List](/fig/CO320-01_COMgmtOverviewList_2019-09-06.png) 4. Fill in the fields from the **Metadata** section of [CO Planning Worksheet :memo:](/files/handouts/CO320-01_COPlanningWorksheet.pdf): a. **The name of your CO.** This name will be displayed on lists and elsewhere. It is a good idea for this name to be descriptive, but relatively short. @@ -133,9 +133,9 @@ We will now implement what you have specified on your worksheets. 6. Navigate back to the Collaborations List by selecting "Collaborations" from the menu. 7. From the Collaborations list page, click on the name of the Collaboration that you just created. -8. In the CO menu, click on the "Configuration" link to see the list of customizations that you can make. Click on the first link, "CO Settings" to adjust the settings. +8. In the CO menu, click on the "Configuration" link to see the list of customizations that you can make. Click on the first link, **CO Settings** to adjust the settings. -![Screen shot - Navigate to COSettings Configuration > CO Settings](/fig/CO310-01_COSettings_2019-09-06.png) +![Screen shot - Navigate to COSettings Configuration > CO Settings](/fig/CO320-01_COSettings_2019-09-06.png) 9. Using the values that you put in your [[CO Planning Worksheet :memo:](/files/handouts/CO320-01_COPlanningWorksheet.pdf), adjust the settings for your CO. 10. Click the `SAVE` button to save your work. @@ -147,25 +147,25 @@ Now that you have created a CO, you should set up at least one person as its adm 11. Ensure that you are signed in and are looking at the CO that you created. 12. Navigate to the Organizational Identity List using the menu on the left by clicking **People** > **Organizational Identities** -![Screen shot - Navigate to People > Organizational Identities](/fig/CO310-02_NavToOrgIdentitiesList.png) +![Screen shot - Navigate to People > Organizational Identities](/fig/CO320-01_NavToOrgIdentitiesList.png) 13. Click on the **Add a New Organizational Identity** link to open a form to create a new `Org Identity`:gear:. _NOTE: generally you will not be performing this function manually, so we will include the minimum attributes and information here._ -![Screen shot - click Add a New Organizational Identity](/fig/CO310-02_CreateNewOrgIdentity.png) +![Screen shot - click Add a New Organizational Identity](/fig/CO320-01_CreateNewOrgIdentity.png) 14. Fill in the form for yourself. The only required information is a **Given Name**. Feel free to fill in as much or as little as you would like. When you are finished, click the **ADD** button to save the new Organizational Identity. 15. You will need an email address associated with this `Org Identity`:gear to create a `CO Person`:gear: that can be turned into an administrator. Add an email address by clicking the **Add** button in the Email addresses section. Fill in the form that is presented, and click the **ADD** button to add the email address. -![Screen shot - click Add Email](/fig/CO310-02_AddEmail.png) +![Screen shot - click Add Email](/fig/CO320-01_AddEmail.png) 16. Now that you have an `Org Identity`:gear: with an email address, you can invite this person (you!) to be a member of your `CO`:gear:. On the menu on the left, select **People** > **Invite** to start the process. This action will bring you to a list of `Org Identities`:gear: that both have an email address, and has not yet a part of the `CO`:gear: or been invited to join. You will see the `Org Identity`:gear: that you created on this list. -![Screen shot - Find a person to invite to your CO](/fig/CO310-02_StartInvitation.png) +![Screen shot - Find a person to invite to your CO](/fig/CO320-01_StartInvitation.png) 17. Click the **Invite** button, review the form that appears as a result, and then click the "SEND INVITE" button. This action will send an invitation email to the address stored, and will add a `CO Person`:gear: attached to the `Org Identity`:gear: to the `CO`:gear:. This means that this new `CO Person`:gear: will appear in the population list for the CO. (The population list appears once the invitation is sent.) -![Screen shot - My Population List](/fig/CO310-02_MyPopulation.png) +![Screen shot - My Population List](/fig/CO320-01_MyPopulation.png) 18. Let's edit the `CO Person`:gear: directly to complete the process. Click the **Edit** button for the newly created `CO Person`:gear: to display the edit screen. Notice that this person was automatically added to the CO:members:all group. @@ -173,7 +173,7 @@ Now that you have created a CO, you should set up at least one person as its adm * Change the **Status** in the **Person Attributes** section to **Active** and click the **SAVE** button. (This action will result in the person also being added to the CO:members:active group) * Add the person to the CO:admins group. In the **Groups** section, click the **Manage Group Memberships** link. for the CO:admins group, check the **Member** checkbox in the **Actions** column. Click the **SAVE** button at the bottom of the list to save this action. Navigate back to the `CO Person`:gear: to check that this person is now a part of the administrators group for the `CO`:gear: -![Screen shot - CO Person Edit screen with "Manage Group Memberships" highlighted](/fig/CO310-02_ManageGroupMemberships.png) +![Screen shot - CO Person Edit screen with "Manage Group Memberships" highlighted](/fig/CO320-01_ManageGroupMemberships.png) CONGRATULATIONS!! You have just created and configured your first CO. @@ -201,21 +201,19 @@ OBJECT | DESCRIPTION `Identity Source`:gear: | Information about a person as obtained from an external source such as LDAP, netFORUM or ORCID. `CO Person Role`:gear: | the representation of a person's role in COmanage. This object describe the person's role with certain collections of people within your organization or collaboration. These objects are attached to :gear: `CO Person` objects; there may be any number of Roles. -`CO Group`:gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons`:gear: - ## CO Person Roles :crown: ROLE | DESCRIPTION ---- | ----------- `CMP Administrators`:crown: | CMP Administrators are effectively super users, with the ability to perform almost all operations on the platform. -`CO`:gear: Administrators | `CO`:gear: Administrators are super users _within a CO_. +`CO Administrators`:crown: | `CO`:gear: Administrators are super users _within a CO_. These individuals belong to the CO:admins group of the `CO`:gear:. `System Administrators`:crown: | System Administrators have privileges that enable them to maintain the COmanage application. -## Worksheets +## Worksheets :memo: WORKSHEET | DESCRIPTION --------- | ----------- -[Modeling Organization :memo:](/files/handouts/CO310-ModelingOrgs.pdf) | Planning sheet used in this lesson for understanding how the parts of the COmanage Organization fit together. +[Modeling Organization :memo:](/files/handouts/CO320-ModelingOrgs.pdf) | Planning sheet used in this lesson for understanding how the parts of the COmanage Organization fit together. [CO Planning Worksheet :memo:](/files/handouts/CO320-01_COPlanningWorksheet.pdf) | Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance. ## Slides diff --git a/_episodes/02-cous.md b/_episodes/02-cous.md index 676aba6..0a4f186 100644 --- a/_episodes/02-cous.md +++ b/_episodes/02-cous.md @@ -1,7 +1,7 @@ --- title: "The COUs" -teaching: 20 -exercises: 0 +teaching: 10 +exercises: 20 questions: - "Question here" objectives: @@ -34,7 +34,7 @@ Any `CO Person`:gear: in the `CO`:gear: can be part of any of the `COUs`:gear: i The attributes (information) stored in the `CO Person Role`:gear: object typically includes * Link to the associated `CO Person`:gear: who is connected to the `COU`:gear: -* Link to the person who is sponsoring the `CO Person`:gear:. `Sponsors`:gear: are usually used in relation to guest systems. We'll talk more about `Sponsors`:gear: later. +* Link to the person who is sponsoring the `CO Person`:gear:. Sponsors are usually used in relation to guest systems. We'll talk more about sponsors when we talk about enrollment workflows. * Status * Personal information about the person * Date of birth @@ -50,7 +50,7 @@ These roles also can include information about the percent time the registered p As with `CO Persons`:gear:, each `CO Person Role`:gear: has a status related to it. The list of possible values is identical to that we reviewed in the previous lesson. -When a `CO Person`:gear: is connected to one or more `CO Person Roles`:gear:, the status of the `CO Person` is calculated from that of the associated Roles based on the "most preferred" status. "Most preferred" is currently defined as the order in the status table (repeated here from the discussion about `CO Person` status in the previous lesson.) +When a `CO Person`:gear: is connected to one or more `CO Person Roles`:gear:, the status of the `CO Person`:gear: is calculated from that of the associated Roles based on the "most preferred" status. "Most preferred" is currently defined as the order in the status table (repeated here from the discussion about `CO Person`:gear: status in the previous lesson.) Active statuses are most preferred, followed by expired statuses, followed by invitation statuses. @@ -77,23 +77,74 @@ Preference | Status | Description `COU Administrators`:crown: can be defined for each `COU`:gear:, giving them the ability to perform lifecycle management operations on the `CO People`:gear: who have `CO Person Roles`:gear: associated with the COU that they manage. -Unit Administrators have limited privileges within the CO, generally related to the ability to enroll and manage populations within the CO Unit (COU). +--- -Unit Administrators are configured by adding the appropriate Organizational Identity to the CO (if not already done), and then adding the corresponding person to the _CO:COU:COU-Name:admins_ group (v2.0.0 and later) or _admin:COU-Name_ group (prior to v2.0.0) within the CO. +# Hands on - The organization model - COUs -# About Sponsors +![Interactive system activity](/assets/img/hands-on-keyboard.png) +Let's add to the organizational model that we're using as an example and its related worksheet, [Modeling Organization :memo:](/files/handouts/CO320-ModelingOrgs.pdf). -# Administrator Roles +_[INSTUCTOR NOTE: it's a good idea to see which workshop participants have natural COUs in their organizations, and use this opportunity to clarify the purpose of a COU. If no one has natural COUs, the interactive part of this episode can be skipped OR the participants can go through this exercise, creating two COUs and using the content below to highlight a common use case for multiple COUs. If there is time, it is best to keep this section in.]_ + +Your organization may not need more than one COU. + +On this worksheet you will see spaces to describe two COUs. Write the name of two of your COUs in these sections. If your organization doesn't have COUs, lets use these two as examples: + +field | COU #1 | COU #2 +----- | ------ | ------ +Name | Main university | Medical school +Description | A sub-unit containing the people and policies related to the **main university**. This is a top-level sub-unit. | A sub-unit containing the people and policies related to the **university's medical school**. This is a top-level sub-unit. +Parent COU | _[blank]_ | _[blank]_ + +You can optionally include this information on the [COU Planning Worksheet :memo:](/files/handouts/CO320-02_COUPlanningWorksheet.pdf) + +[5 min] + +--- + +# Hands on - Create `COUs`:gear: + +![Interactive system activity](/assets/img/hands-on-keyboard.png) -COmanage Registry defines three types of administrators. +We will now implement what you have specified on your worksheets. -## Unit (COU) Administrators +## Sign into the Registry -Collaboration Administrators with sophisticated administrative requirements may optionally define Unit Administrators. +1. Using the credentials you specified as part of the COmanage setup (or the `CO Administrator`:crown: that you established in the last section), sign into the system. +2. Navigate to your `CO`:gear:. If necessary, select your `CO`:gear: by selecting **Collaborations** from the menu on the left, and then selecting your Collaboration. -COU Administrators can be defined for each COU, giving them the ability to perform lifecycle management operations on the CO People who have CO Person Roles associated with the COU that they manage (or any child COUs of that COU). +## Create a `COU`:gear: +**REQUIRED ROLE**: `CMP Administrator`:crown: OR `CO Administrator`:crown: + +3. In the CO menu, click on the "Configuration" link to see the list of customizations that you can make. Click on the link labeled **COUs** to see the list of `COUs`:gear: for the `CO`:gear:. + +4. Click the **Add a New COU** link above the table to create a new COU. Fill in the form using the values that you included on your worksheet and click the **ADD** button to add the `COU`:gear:. + +5. Repeat for the second `COU`:gear:. When you return to the COU List, you will see the two COUs that you created. They can be edited from this page if needed. + +## Establish a `COU Administrator`:crown: + +Each COU can have its own `COU Administrator`:crown:. Manually designating the administrators is a process similar to the one that we followed to create a `CO Administrator`:crown:. + +6. Ensure that you are signed in and are looking at the CO that you created. From the COU list page, you can use the breadcrumb links near the top of the screen to navigate back to your CO. There are two common paths for manually designating `COU Administrators`:crown:. We will use a different process for each of the COUs that we created. +7. From the `CO Person`:gear: + * From the menu on the left select **People** > **My Population** to see the list of `CO People`:gear: in your `CO`:gear: + * Click the **Edit** button next to the name of the person you set up in the previous lesson. + * Scroll to the **Groups** section, and click the **Manage Group Memberships** link. On the list of groups you will now see admins, active, and all groups for each of your `COUs`:gear: as well as those for the full `CO`:gear: + * Make this person the owner of the admin group for your first `COU`:gear: - check the **Owner** checkbox for (only) the first `COU`:gear: that you created. Click the **SAVE** button to save these changes. +8. From the groups list: + * From the menu on the left, select **Groups** + * Click the **Edit** button for the admin group for the second `COU`:gear: that you created to display the group management page. + * Scroll to the bottom of the page to see the list of group members. Click the **Manage Group Memberships** link to see a list of people that you can add to the group. + * From the group membership management list, check the "Member" permission to make this person a member of the admin group for the second `COU`:gear: that you created. Click the **SAVE** button to save this change. + +![Screen shot - Manage Group Membership](/fig/CO320-02_ManageGroupMembers.png) + +CONGRATULATIONS!! You have just created and configured your first COUs. + +[15 min] --- @@ -103,27 +154,22 @@ COU Administrators can be defined for each COU, giving them the ability to perfo OBJECT | DESCRIPTION ------ | ----------- -`CO`:gear: | any formal or informal group of individuals that work collaboratively in a digital setting. They have a goal of a shared infrastructure that supports their collaborations so that the traditional limitations of localized applications may be overcome. +`COU`:gear: | an organizational structure within a CO that differs in how individuals join and/or leave the group, how applications get provisioned or deprovisioned, who manages person membership and privileges in the group, or in the information stored or used about members of the group. `CO Person`:gear: | the representation of a person in COmanage -`Identity Source`:gear: | Information about a person as obtained from an external source such as LDAP, netFORUM or ORCID. `CO Person Role`:gear: | the representation of a person's role in COmanage. This object describe the person's role with certain collections of people within your organization or collaboration. These objects are attached to :gear: `CO Person` objects; there may be any number of Roles. -`CO Group`:gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons`:gear: - ## CO Person Roles :crown: ROLE | DESCRIPTION ---- | ----------- -`CMP Administrators`:crown: | CMP Administrators are effectively super users, with the ability to perform almost all operations on the platform. -`CO`:gear: Administrators | `CO`:gear: Administrators are super users _within a CO_. -`System Administrators`:crown: | System Administrators have privileges that enable them to maintain the COmanage application. +`COU Administrators`:crown: | Individuals that have the ability to perform lifecycle management operations on the `CO People`:gear: who have `CO Person Roles`:gear: associated with the `COU`:gear:. ## Worksheets WORKSHEET | DESCRIPTION --------- | ----------- -[Modeling Organization :memo:](/files/handouts/CO310-ModelingOrgs.pdf) | Planning sheet used in this lesson for understanding how the parts of the COmanage Organization fit together. -[CO Planning Worksheet :memo:](/files/handouts/CO320-01_COPlanningWorksheet.pdf) | Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance. +[Modeling Organization :memo:](/files/handouts/CO320-ModelingOrgs.pdf) | Planning sheet used in this lesson for understanding how the parts of the COmanage Organization fit together. +[COU Planning Worksheet :memo:](/files/handouts/CO320-02_COUPlanningWorksheet.pdf) | Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance. ## Slides @@ -131,7 +177,9 @@ To be included --- -NEXT SECTION: [2. The COU](/_episodes/02-cous.md) +PREVIOUS SECTION [1. The CO](/_episodes/01-co.md) + +NEXT SECTION: [3. About Departments](/_episodes/03-departments.md) LESSON OVERVIEW: [CO320 - Modeling Your Organization in COmanage](../index.md) diff --git a/_episodes/03-departments.md b/_episodes/03-departments.md index 8d210d8..c742052 100644 --- a/_episodes/03-departments.md +++ b/_episodes/03-departments.md @@ -30,12 +30,12 @@ CO Departments are specifically intended to be used with [Registry Services](htt # Terminology & resources -## COmanage Objects +## COmanage Objects :gear: OBJECT | DESCRIPTION ------ | ----------- -`CO Person` :gear: | the representation of a person in COmanage -`CO Group` :gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons` :gear: +`CO Person`:gear: | the representation of a person in COmanage +`CO Group`:gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons`:gear: ## Worksheets diff --git a/_episodes/04-groups.md b/_episodes/04-groups.md index 35be950..1d4a47c 100644 --- a/_episodes/04-groups.md +++ b/_episodes/04-groups.md @@ -112,8 +112,8 @@ If at least one CO Service is configured with Unauthenticated User visibility, t OBJECT | DESCRIPTION ------ | ----------- -`CO Person` :gear: | the representation of a person in COmanage -`CO Group` :gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons` :gear: +`CO Person`:gear: | the representation of a person in COmanage +`CO Group`:gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons`:gear: ## Worksheets diff --git a/_episodes/05-yourOrg.md b/_episodes/05-yourOrg.md index 743ffb3..a4af679 100644 --- a/_episodes/05-yourOrg.md +++ b/_episodes/05-yourOrg.md @@ -12,58 +12,22 @@ keypoints: # 5. Setting up your organization -# Then IMPLEMENT IT... - -## Create a CO - -![Interactive system activity](../assets/img/hands-on-keyboard.png) - -**REQUIRED ROLE**: Platform Administrator - -1. Sign into COmanage as a Platform Administrator. Once you sign in you will see a list of available collaborations. -2. Since you want to create a new CO, from the menu, select Platform > COs to display the CO Management Overview List. - -![Navigate to the CO Management Overview List](../fig/CO301-04_COMgmtList_2019-09-06.png) - -3. Click the "Add CO" link above the table on the right side to add a new CO. - -![CO management Overview list](../fig/CO301-04_COMgmtOverviewList_2019-09-06.png) - -4. Fill in the fields: - a. **The name of your CO.** This name will be displayed on lists and elsewhere. It is a good idea for this name to be descriptive, but relatively short. - b. **Description.** Write a short description of your CO. This description will be helpful for those who may not be familiar with your CO's name. - c. **Status.** There are three choices for the status: - * Active - you will select this one. Your CO will be immediately active upon its creation. - * Suspended - Useful if you do not want your CO to be active. - * Template - Useful if you want to create several COs based on the configuration from this one. - -## Configure your CO - -![Interactive system activity](../assets/img/hands-on-keyboard.png) - -### Settings - -The settings section for your CO enables you to configure the CO behavior. While there are several settings, we will only discuss the most common ones today. More details can be found on the [documentation page in the COmanage wiki](https://spaces.at.internet2.edu/display/COmanage/How+to+Configure+a+CO). +Platform Administrators are configured by [adding the appropriate Organizational Identity](https://spaces.at.internet2.edu/display/COmanage/Default+Registry+Enrollment) to the COmanage CO, and then adding the corresponding person to the CO:admins group (v2.0.0 and later) or admin group (prior to v2.0.0) within the COmanage CO. -**REQUIRED ROLE**: Platform Administrator | Collaboration (CO)Administrator - - -1. From the Collaborations list page, click on the name of the Collaboration that you want to configure. -2. In the CO menu, click on the "Configuration" link to see the list of customizations that you can make. Click on the first link, "CO Settings" to adjust the settings. - -![Navigate to COSettings Configuration > CO Settings](../assets/img/CO301-04_COSettings_2019-09-06.png) +# Then IMPLEMENT IT... -3. Using the values that you put in your [CO Worksheet](/files/handouts/COmanage Planning_ CO_Worksheet.pdf), adjust the settings for your CO. -4. Click the `SAVE` button to save your work. # Implement a group! // NOTE: this section needs to be confirmed & screen shots added. +### CO Admins + +Collaboration Administrators are configured by adding the appropriate Organizational Identity to the CO (if not already done), and then adding the corresponding person to the CO:admins group (v2.0.0 and later) or admin group (prior to v2.0.0) within the CO. ## Create a Group -![Interactive system activity](../assets/img/hands-on-keyboard.png) +![Interactive system activity](/assets/img/hands-on-keyboard.png) **REQUIRED ROLE**: Platform Administrator (or maybe this is "Any CO Person?", at least by default.) @@ -182,12 +146,12 @@ Prior to v2.0.0: # Terminology & resources -## COmanage Objects +## COmanage Objects :gear: OBJECT | DESCRIPTION ------ | ----------- -`CO Person` :gear: | the representation of a person in COmanage -`CO Group` :gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons` :gear: +`CO Person`:gear: | the representation of a person in COmanage +`CO Group`:gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons`:gear: ## Worksheets diff --git a/fig/CO310-02_AddEmail.png b/fig/CO320-01_AddEmail.png similarity index 100% rename from fig/CO310-02_AddEmail.png rename to fig/CO320-01_AddEmail.png diff --git a/fig/CO310-01_COMgmtList_2019-09-06.png b/fig/CO320-01_COMgmtList_2019-09-06.png similarity index 100% rename from fig/CO310-01_COMgmtList_2019-09-06.png rename to fig/CO320-01_COMgmtList_2019-09-06.png diff --git a/fig/CO310-01_COMgmtOverviewList_2019-09-06.png b/fig/CO320-01_COMgmtOverviewList_2019-09-06.png similarity index 100% rename from fig/CO310-01_COMgmtOverviewList_2019-09-06.png rename to fig/CO320-01_COMgmtOverviewList_2019-09-06.png diff --git a/fig/CO310-01_COSettings_2019-09-06.png b/fig/CO320-01_COSettings_2019-09-06.png similarity index 100% rename from fig/CO310-01_COSettings_2019-09-06.png rename to fig/CO320-01_COSettings_2019-09-06.png diff --git a/fig/CO310-02_CreateNewOrgIdentity.png b/fig/CO320-01_CreateNewOrgIdentity.png similarity index 100% rename from fig/CO310-02_CreateNewOrgIdentity.png rename to fig/CO320-01_CreateNewOrgIdentity.png diff --git a/fig/CO310-02_ManageGroupMemberships.png b/fig/CO320-01_ManageGroupMemberships.png similarity index 100% rename from fig/CO310-02_ManageGroupMemberships.png rename to fig/CO320-01_ManageGroupMemberships.png diff --git a/fig/CO310-02_MyPopulation.png b/fig/CO320-01_MyPopulation.png similarity index 100% rename from fig/CO310-02_MyPopulation.png rename to fig/CO320-01_MyPopulation.png diff --git a/fig/CO310-02_NavToOrgIdentitiesList.png b/fig/CO320-01_NavToOrgIdentitiesList.png similarity index 100% rename from fig/CO310-02_NavToOrgIdentitiesList.png rename to fig/CO320-01_NavToOrgIdentitiesList.png diff --git a/fig/CO310-02_StartInvitation.png b/fig/CO320-01_StartInvitation.png similarity index 100% rename from fig/CO310-02_StartInvitation.png rename to fig/CO320-01_StartInvitation.png diff --git a/fig/CO320-02_ManageGroupMembers.png b/fig/CO320-02_ManageGroupMembers.png new file mode 100644 index 0000000..52da500 Binary files /dev/null and b/fig/CO320-02_ManageGroupMembers.png differ diff --git a/files/handouts/CO320-02_COUPlanningWorksheet.pdf b/files/handouts/CO320-02_COUPlanningWorksheet.pdf new file mode 100644 index 0000000..a305284 Binary files /dev/null and b/files/handouts/CO320-02_COUPlanningWorksheet.pdf differ diff --git a/index.md b/index.md index bdafb90..aacae9d 100644 --- a/index.md +++ b/index.md @@ -25,10 +25,12 @@ When using COmanage with your organization or collaboration, the people that you Time | Section | Description ---- | ------- | -----------   | [Setup](/setup.md) | Prepare for the lesson -00:45 | [1. The CO](/_episodes/01-co.md) | Collaborative Organizations, what they are and how they are used. +00:55 | [1. The CO](/_episodes/01-co.md) | Collaborative Organizations, what they are and how they are used. +00:30 | [2. The COUs](/_episodes/02-cous.md) - CO Units | COUs are major subgroups of COs. When to use them and how to set them up. + _The actual schedule may vary slightly depending on the topics and exercises chosen by the instructor._ -2. [2. The COUs](/_episodes/02-cous.md) - CO Units + 3. [3. About CO Departments](/_episodes/03-departments.md) - 4. [4. About CO Groups](/_episodes/04-groups.md) \ No newline at end of file