> For the complete documentation index, see [llms.txt](https://docs.revrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revrobotics.com/rev-professional-development-technical-path/gs/config/manage.md).

# Keeping Track of Configurations

Multiple configurations can be created on the Control Hub to be switched between for different projects or classes. 

Creating a new configuration may be better than attempting edit an existing one, especially if it is being created to test an idea, for example, or certain devices are being added. 

Some sensors, like the color sensor, once added to the configuration will cause a program to error out if they are removed physically, but not from the configuration!

## How to keep track?

Keeping track of configurations can be as easy as making a small table record with the type of part, the port it's connected to, and the assigned named. If parts are changed or renamed, this chart can be updated. 

Here is an example format we commonly follow when creating guides we want others to follow:

| Port                  | Device Type       | Device Name |
| --------------------- | ----------------- | ----------- |
| Motor Port 0          | Core Hex Motor    | coreHex     |
| Motor Port 1          | HD Hex Motor      | ultraHex    |
| Servo Port 0          | Smart Robot Servo | servo       |
| Digital Sensor Port 1 | Touch Sensor      | touchSensor |

{% hint style="info" %}
Remember that device names in configuration are case sensitive! 
{% endhint %}

A handout is provided here to use with students or while continuing through this training: 

{% file src="/files/9N8WSTzoX25J1kCiPEUf" %}

Space has been provided on this tracker for sensors and parts not found in the EDU Kit V2.