Updates the instructions for new ILT lab environment

To start, in the left sidebar, select **Groups**.

1. In the **Groups** section, select the dropdown arrow on the left of **Training Users**.

1. In the **Groups** section, select the dropdown arrow on the left of **Events**.

1. Below **Training users**, you should now see a group with a name like **Session XXXXXXXX**.

1. Click the dropdown arrow next to the **Session** group. You should now see a group named **My Test Group - XXXXXXXX**. Click this group to access it.

1. Click the dropdown arrow next to the **Session** group. You should now see a group named **Group XXXXXXXX**. Click this group to access it.

This navigation shows an example of groups and subgroups. In the ILT GitLab instance, the **Training Users** group is a top-level group. This means that it is not part of any other groups in the instance. The **Training Users** group contains a set of subgroups, which represent classes running in the instance. Each of these subgroups is given a name like **Session XXXXXXXX**. Inside of these groups is a set of subgroups, one group for each student in the class. The **My Test Group** subgroup is your own group, which you can organize and modify in any way you like.

This navigation shows an example of groups and subgroups. In the ILT GitLab instance, the **Training Users** group is a top-level group. This means that it is not part of any other groups in the instance. The **Training Users** group contains a set of subgroups, which represent classes running in the instance. Each of these subgroups is given a name like **Session XXXXXXXX**. Inside of these groups is a set of subgroups, one group for each student in the class. The **Group XXXXXXX** subgroup is your own group, which you can organize and modify in any way you like.

## Task B. Creating a Group Structure

To start, make sure you are in the **My Test Group** subgroup. For this task, imagine you are working at a company with two departments: Development, and QA. These departments have the following projects:

To start, make sure you are in the **Group XXXXXXX** subgroup. For this task, imagine you are working at a company with two departments: Development, and QA. These departments have the following projects:

- Development: A mobile and desktop version of an application named `Cool App`. Of note, `Cool App` contains many microservices spread over many repositories for both versions.

- QA: Two testing frameworks, one for the mobile version of `Cool App` and one for the desktop version. Both frameworks are monolithic, stored in a single project.

1. In the **Subgroup name**, enter `Development`. Leave all other options as default and select **Create subgroup**.

1. At the top of the page, you will see a set of breadcrumbs which shows your location in the application. Click **My Test Group** to return to your main group.

1. At the top of the page, you will see a set of breadcrumbs which shows your location in the application. Click **Group XXXXXXX** to return to your main group.

1. From here, you will now see your `Development` group. Select **New subgroup** to create your group for QA.

1. In the **Subgroup name**, enter `QA`. Leave all other options as default and select **Create subgroup**.

1. Select **My Test Group** from the breadcrumbs again to return to your main group. You will now see two groups: `Development` and `QA`.

1. Select **Group XXXXXXX** from the breadcrumbs again to return to your main group. You will now see two groups: `Development` and `QA`.

    Next, we can structure subgroups for both team's projects. Since the development applications have many projects, it makes sense to create a subgroup for each project type.

## Task C. Creating a repository

Let's create a new repository for the QA team. Select the `QA` group in your **My Test Group**. From here:

Let's create a new repository for the QA team. Select the `QA` group in your **Group XXXXXXX**. From here:

1. Select **New project**.

## Task B. Create organizational subgroups

1. Navigate to your personal top-level group by going to `https://ilt.gitlabtraining.cloud/training-users/session-<INVITATION_CODE>/<USERNAME>`, replacing the **<INVITATION_CODE>** with your provided code, and **<USERNAME>** with your username. If you are unsure of what your username is, click on the profile picture in the top right corner, and copy the username provided without the @ symbol.

1. Navigate to your personal top-level group by going to `ilt.gitlabtraining.cloud`, and click on **Groups**. In your group section, click on the Arrow next to **Events**, and then click on the arrow next to **Session XXXXXXXX apm**, with the X's replaced with random letters and numbers. There should be a group called **Group YYYYY**, with the Y's replaced with random letters and numbers. 

1. Click on the group titled **Group YYYYYY**. This will take you to that group. 

1. Click the **New Subgroup** button in the top right corner.

> Epics provide a way to organize and manage a set of issues and sub-epics that share a strategic theme. In addition to logical grouping, epics enable project managers to perform higher level planning and build a roadmap with visual status tracking. You can read more about epics in the [documentation](https://docs.gitlab.com/ee/user/group/epics/).

1. *In the lab environment browser tab,* at the top of the page, Click on **My Test Group - XXXXX**, where the X's are replaced by your username.

1. *In the lab environment browser tab,* at the top of the page, Click on **Group XXXXX**, where the X's are replaced by random letters and numbers.

1. On the groups page, click on the **Awesome Inc** subgroup. Inside the subgroup, click **Software**.