# Working with Process Hierarchy (Document Control)
QualityOne Vaults allow you to display business processes and associated documents in a hierarchical interface. _Visual Hierarchy_ records store information about a Process and the relationships between Processes. You can establish parent-child relationships between Associated Processes up to five (5) levels down from the parent record.
The _Process Hierarchy_ page displays the _Visual Hierarchy_ records according to the relationships between the Associated Processes. You can associate relevant supporting documents to one (1) or many Processes.
Depending on your Admin's configuration, object, field, and section labels may appear differently than the labels mentioned in this article.
## Creating Visual Hierarchy Records {#creating-records}
Before you can populate your Hierarchy, your Admin must create the appropriate object types for the _Visual Hierarchy_ object. Once the object types become available, you can create a set of associated _Visual Hierarchy_ records to populate the Hierarchy structure and pages.
During record creation, you can arrange the position of each record to determine where it should display on the _Process Hierarchy_ and _Process Details_ pages by establishing the parent-child relationships.
To create and arrange _Visual Hierarchy_ records:
1. Navigate to **Business Admin > Objects > Visual Hierarchies** or to a custom tab.
2. Click **Create**.
3. Enter a **Name** and **Description**. Vault displays the _Name_ as a clickable item in the Viewer and displays the _Description_ in the _Process Details_ page.
4. Optional: In the _Position within Parent_ field, enter a value to determine the order in which Vault should display the records in the Viewer of the Hierarchy page and the Associated Processes of the _Process Details_ page. If you do not enter a value, the record will list under any record that contains a position value. If multiple records contain the same value or are blank, Vault resolves the conflicts by displaying the records in alphabetical order.
5. Optional: In the _Icon_ field, enter a valid icon label. Use the list of valid icons to enter the appropriate label.
6. Click **Save**.
By default, Vault immediately displays the newly-created _Visual Hierarchy_ records in the Viewer to users with the appropriate permissions. Depending on your Admin's configuration, _Visual Hierarchy_ records may need to go through a review workflow or lifecycle state change before displaying in the Viewer.
### Reparenting Visual Hierarchy Records {#reparenting-records}
You can reparent _Visual Hierarchy_ records between records of the same object type.
To reparent a _Visual Hierarchy_ record:
1. Navigate to the _Visual Hierarchy_ record you want to reparent.
2. Click **Edit**.
3. Select a new target parent in the _Parent_ field.
4. Click **Save**.
## Adding Documents to a Visual Hierarchy Record {#adding-documents}
To display a collection of relevant supporting documents in the _Process Details_ page, you must add the associated _Documents_ to the appropriate _Visual Hierarchy_ record by creating an associated _Hierarchy Document_ record.
To add _Documents_ to a _Visual Hierarchy_ record:
1. Navigate to the appropriate _Visual Hierarchy_ record and click **Create** in the _Hierarchy Documents_ section.
2. Choose one (1) or more **Documents**.
3. Click **Save**.
Vault populates the _Documents_ section of the _Process Details_ page with a filterable list of the added documents.
## Limitations {#limitations}
The following limitations apply to Process Hierarchy:
* Depending on your Admin's configuration, you can create a maximum of three (3) _Visual Hierarchy_ records without a parent record and a maximum of five (5) levels of parent-child record relationship.
* Depending on your Admin's configuration, each parent _Visual Hierarchy_ record can have up to ten (10) child records.
* You cannot associate or reparent _Visual Hierarchy_ records of a given object type with a parent record of a different _Visual Hierarchy_ object type.
* You cannot convert a child _Visual Hierarchy_ record into a root record, and a root record cannot be converted to a child record.