Note: Depending on your Vault’s creation date and which features are currently enabled and configured, some of the steps described in this article may be unavailable or already complete in your Vault.
) icon.
4. Optional: Enter a **Section Label**.
5. Optional: In the **Show the section only in these lifecycle states** field, select one (1) or more lifecycle states. This option appears only if the object uses a [lifecycle](/en/lr/29798/).
6. Optional: Enter **Section Help** content to provide the user with any relevant information. Help content appears below the section label.
7. Select up to ten (10)
[supported][2] _Project_ fields to **Display Project columns**. Drag and drop fields to determine the order of columns to display to users.
8. Select up to ten (10) [supported][2] _Claim_ fields to **Display Claim columns**. Drag and drop fields to determine the order of columns to display to users.
9. Select up to ten (10) [supported][2] _Local Adaptation_ fields to **Display Local Adaptation columns**. Drag and drop fields to determine the order of columns to display to users.
10. Optional: Select **Expand section by default**.
11. Click **Done**.
12. Click **Save**.
### Supported Fields {#fields}
Vault supports the following object field types in _Display [Object] column_ fields:
* Component (for Lifecycle states)
* Date
* Number
* Object
* Object Reference
* Picklist
* Text/Long Text
* Yes/No
* Lookup (so long as the type is a supported type listed above)
The _Display [Object] column_ field always includes the _Name_field as the first column.
## Configuring User Permissions {#user-perms}
You must ensure users have a security profile with permissions to access the appropriate objects and object fields in order to see the _Hierarchy_ section on an object's detail page, including _Read_ permission on the _Claim Project Join_ object and _Project Local Adaptation Join_ object.
In addition, users must have field-level permissions on the _Project_, _Claim_, and _Local Adaptation_ objects to be able to see all configured columns in the viewer.
### Understanding Filter Permissions {#filter-perms}
Lists of [pre-filtered field values][3] are pulled into the hierarchy viewer. Review the following details about pre-filtered field values:
* Users without _Read_ permission on the _Product_ object continue to see _Product ID_ (`name__v`) values where the _Product_ is linked to the _Claims_ for which they have appropriate permissions.
* Users without _Read_ permission on the _Project Product Join_ object see _Product ID_ (`name__v`) values where the _Product_ is linked to the _Claims_ for which they do have appropriate permissions.
* Users without _Read_ permission on the _Project Country Join_ object see _Location_ (`country__v`) values where the _Location_ is linked to _Local Adaptation_ records for which they do have appropriate permissions.
* Users without _Read_ permission on the _Product_ field of the _Claim_ object or the _Location_ (`country__v`) field of the _Local Adaptation_ object cannot see the _Product_ or _Location_ field columns in the hierarchy viewer and cannot select filters for these fields or see pre-filtered field values.
## Related Permissions
You can complete all the steps in this article with the standard _System Administrator_ or _Vault Owner_ security profile. If your Vault uses custom security profiles, your profile must grant the following [permissions](/en/lr/22824/):
| Type | Permission | Controls |
|---|---|---|
| Security Profile | Admin: Configuration: Objects: Create, Edit | Ability to create and modify Vault objects. |
| Security Profile | Admin: Security: Permission Sets: Edit | Ability to modify permission sets for users. |