Resource Relationships

Resources can be related to each other in various ways.

One-to-Many: A single resource can be associated with multiple instances of another resource.
Many-to-One: Multiple instances of a resource can be associated with a single instance of another resource.
One-to-One: A single instance of a resource is associated with exactly one instance of another resource.

The following table outlines the relationships between different resources in the system.

Relationship Aliases: When a resource has multiple relationships to the same target, the aliases are shown in parentheses. Use the alias name (not the resource name) in your with block. For example, applications has three relationships to users — use "application_owner", "business_owner", or "it_owner" instead of "users".

Resource	One-to-Many	Many-to-One	One-to-One
alerts		applications, contracts
application_licenses		applications, application_users
application_users	application_licenses	applications, users
applications	alerts, application_licenses, application_users, contract_line_items, contracts, payments, po_line_items, savings_events, view_applications	users (application_owner, business_owner, it_owner)	integrations, usage_connect
contract_line_items		applications, contracts
contracts	alerts, contract_line_items	applications
integrations			applications, usage_connect
payments		applications, po_line_items, users, zybrary
po_line_items	payments, unmatched_payments	applications, purchase_orders
purchase_orders	po_line_items, unmatched_payments	suppliers
savings_events		applications
suppliers	purchase_orders, unmatched_payments
unmatched_payments		purchase_orders, po_line_items, suppliers
usage_connect			applications, integrations
users	application_users, applications (app_owner_applications, business_owner_applications, it_owner_applications), payments
view_applications		applications, views
view_zylo_users		views, zylo_users
views	view_applications, view_zylo_users
zybrary	payments
zylo_users	view_zylo_users