# Issue Management Administration in CTMS

Your CTMS Vault provides the ability to capture and manage multiple types of _Issues_ across a study country or study site including _Observations_, _Protocol Deviations_, <a href="/en/gr/62007/#mitigation-actions">_Mitigation Actions_</a>
, and any other custom object types. Users can track _Issues_ for follow up, promote or demote them to different object types, and seed them directly into _Monitoring Events_.

<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>: As of 21R1, we recommend that you update the label on the <em>Protocol Deviation</em> (<code class="language-plaintext highlighter-rouge">pdv__ctms</code>) object to <em>Issue</em> in all CTMS Vaults.</p>
    </div>
  </div>
</div>



## Overview

To fully utilize issue management functionality, we recommend that you perform the following configuration tasks in your Vault:
* <a href="/en/gr/32857/#create">Activate</a>
 all relevant _Issue_ object types. Note that only active object types are displayed on the _Quality_ widget on the <a href="/en/gr/39905/#study-quality">CRA Homepage</a>
.
* Create a <a href="/en/gr/26387/">page layout</a>
 for the _Observation_ object type of the _Issue_ object.
* Configure the _Change Issue Type_ <a href="/en/gr/59885/#define-actions">user action</a>
 on the relevant states of the _Issues_ lifecycle so that users can promote and demote _Issues_.
* Update <a href="/en/gr/68407/#related-permissions">permission sets</a>
 to grant users access to _Issue_ objects.
* Optional: Configure the _Monitoring Event_ object and lifecycle to allow _Issues_ to be <a href="/en/gr/42837/#seeding">seeded directly into related _Monitoring Event_ records</a>
.