# Working with Collection Approvals and Versioning

## Approving a Collection {#approving-a-collection}

Once the collection includes all required surveys, languages, schedules, and notifications, you can approve it for use in Veeva eCOA. Approval increments the Version number to the next whole number. For example, Version 1.2 becomes Version 2.0. The approved version is an exact copy of the previous version.

To approve a collection, complete the following steps:

1. Open the collection and select the **Approve** button.
2. Enter a Summary of Changes and select **Approve**.

After approving the first version of the collection (1.0), you will also need to <a href="/en/lr/918800/">deploy it to sites</a> for them to receive the updates. Sites do not receive notifications or see new versions until you initiate deployment.

## Creating a New Collection Version {#creating-a-new-collection-version}

If your study has changes, such as protocol amendments or the addition of new languages, you can create a new version. Each round of UAT also creates another minor version, incrementing the version number by one decimal point. For example, Version 1.2 becomes Version 1.3. A new version is an exact copy of the previous version before changes are made.

You cannot start UAT for a collection until the following requirements are met:

* All translations for all languages are uploaded.
* At least one schedule is configured for each survey.

If you're unable to approve a collection, hover over **Start UAT** to view the list of required actions.

To create a new version of an approved collection, complete the following steps:

1. In Studio, select **New Version**. A new version opens.


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: During the UAT cycle, you can start a new version from the latest minor version or revert back to the last approved major version. After deleting the last minor version, the system will prompt you to choose a base version:<br /></p>
<ol>
  <li>The last superseded minor version: Veeva recommends this option to retain all recent changes.<br /></li>
  <li>The last approved version: Excludes recent minor version changes.</li>
</ol>
    </div>
  </div>
</div>


 {:start="2"}
1. Make necessary changes to the new version.
2. Select **Start UAT**, and enter a Summary of Changes. See <a href="/en/lr/912962/">Performing User Acceptance Testing (UAT) on a Collection</a> for more information.
3. Select **Finish UAT** and complete one of the following steps:
    1. If additional changes are needed, select **No, make changes** and repeat Steps 2 through 4.
    2. If the collection passed UAT, select **Yes, complete UAT**.

The new version is saved. 

## Deleting a Collection

You can delete the following types of collections:

* A newly created collection that has never been approved.
* The latest, unapproved version of a collection.

To delete a collection, complete the following steps:

1. Open the collection and select **Delete Collection** from the **Actions** menu (<i class="far fa-ellipsis-h"></i>).
1. When the confirmation pop-up appears, add a reason and select **Delete**.

The collection version is deleted.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: When creating a new version of a previously approved collection after deleting its latest version, the system will prompt you to choose a base version. Veeva recommends selecting the last superseded minor version to retain all recent changes.</p>
    </div>
  </div>
</div>