---
title: "Can I link a Change Request to a Document at the Organization-level?"
description: "Yes, you can achieve this in a similar manner to linking these items on the project-level. After enabling \" Documents as Items\", you can create the relevant custom items and assign a custom relation."
category: "Frequently Asked Questions"
section: "Traceability"
keywords: ["change request", "custom relation", "impacts", "custom document", "similar", "organization level", "link", "dropdown menu"]
source_url: "https://support.ketryx.com/hc/en-us/articles/42054275357709-Can-I-link-a-Change-Request-to-a-Document-at-the-Organization-level"
last_reviewed: 2026-06-11
---

# Can I link a Change Request to a Document at the Organization-level?

> **In short:** Yes, you can achieve this in a similar manner to linking these items on the project-level. After enabling " Documents as Items", you can create the relevant custom items and assign a custom relation.

Yes, you can achieve this in a similar manner to linking these items on the [project-level](https://docs.ketryx.com/work-instructions/wi-11-document/generalized-documents#add-the-following-configuration-under-custom-relations). After enabling " [Documents as Items](https://docs.ketryx.com/work-instructions/wi-11-document/generalized-documents#enable-documents-as-items)", you can create the relevant custom items and assign a custom relation. Relations that originate from the custom document item at the organization level will not be able to point to change request items within projects. So, you must create a custom relation which originates from the "Change Request" item, and points to your custom document types, similar to the one included below.

{

"CR_DOC": {

"direction": "downstream",

"fieldName": "Impacts document",

"relationName": "impacts document",

"sourceItemTypes": \[\
\
     " **Change Request**"\
\
\],

"reverseFieldName": "Is related to change request",

"targetItemFilter": "type: **LLD,PD**",

"reverseRelationName": "relates to change request",

"traceabilityWidgetAddLabel": "Add impacted document"

},

You must then navigate to "References" of the project of the Change Request item, and add a reference to the "Organization". Then you will be able to see Organization-level documents as options in the custom relation field dropdown menu.

## Related articles

- [Can I create a new/custom Ketryx relation type for the traceability widget?](can-i-create-a-new-custom-ketryx-relation-type-for-the-traceability-widget.md)
- [How could I effectively use change request items in Ketryx? What are some common practices?](how-could-i-effectively-use-change-request-items-in-ketryx-what-are-some-common.md)
- [Why is my custom item type not showing up with default realtions?](why-is-my-custom-item-type-not-showing-up-with-default-realtions.md)
- [How are Change Requests approved in Ketryx—are tickets closed upon approval, and does this happen in the CR or test plan? Can we customize the process to support significance review with fields or workflows as needed?](how-are-change-requests-approved-in-ketryx-are-tickets-closed-upon-approval-and.md)
- [How can I define custom document IDs?](how-can-i-define-custom-document-ids.md)