# Entity Components

Entity components are how a workflow finds, displays, and creates the people and organisations behind every transaction — customers, vendors, partners, and contacts.

The classic pattern is **search → select → display**: an Entity Search drives an Entity 360 (or downstream blocks like Address) once the user picks a result. For Order Form contexts, **Customer/Vendor Selection** plays the same role and integrates with Order Lines.

## Components in this category

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Customer/Vendor Selection</strong></td><td>Entity picker for Order Form pages — drives Address, Order Lines, Customer Field.</td><td><a href="/pages/km19hjFIFOFjRK0yQAJp">/pages/km19hjFIFOFjRK0yQAJp</a></td></tr><tr><td><strong>Entity Search</strong></td><td>Lookup interface for customers, vendors, or partners with configurable result columns.</td><td><a href="/pages/YG0JVvulp0T0QNjVYaQI">/pages/YG0JVvulp0T0QNjVYaQI</a></td></tr><tr><td><strong>Entity 360 View</strong></td><td>Full tabbed profile — metrics, financial, addresses, contacts, attachments, orders, deposits.</td><td><a href="/pages/iZxOk2Qc3Jd4I8EhpErq">/pages/iZxOk2Qc3Jd4I8EhpErq</a></td></tr><tr><td><strong>Support Case</strong></td><td>Inline support-case list and submission form for the selected customer.</td><td><a href="/pages/HJjm2i8TURJ00Z8oJxDL">/pages/HJjm2i8TURJ00Z8oJxDL</a></td></tr><tr><td><strong>Create Entity</strong></td><td>Configurable form for creating new entities — inline or modal.</td><td><a href="/pages/blGPwieua2cDRDY0pp3W">/pages/blGPwieua2cDRDY0pp3W</a></td></tr><tr><td><strong>Address</strong></td><td>Display billing/shipping address from the selected customer, with order-type filtering.</td><td><a href="/pages/mz9aKhtOjrSU4uu6KToN">/pages/mz9aKhtOjrSU4uu6KToN</a></td></tr><tr><td><strong>Select Customer Address</strong></td><td>Lets the user pick from the customer's saved addresses.</td><td><a href="/pages/j6kVrqUIcgwEwgtDlLFv">/pages/j6kVrqUIcgwEwgtDlLFv</a></td></tr><tr><td><strong>Customer Hold Status</strong></td><td>Surfaces credit holds and supports PIN-based manager override.</td><td><a href="/pages/CqpoPOnhKc67FeMefdKr">/pages/CqpoPOnhKc67FeMefdKr</a></td></tr><tr><td><strong>PIN Pad</strong></td><td>Numeric PIN entry for module-wide gates and standalone PIN-required pages.</td><td><a href="/pages/gDdGC4CKyI44d6fINGo5">/pages/gDdGC4CKyI44d6fINGo5</a></td></tr></tbody></table>

## When you'd reach for this category

* **Order Form context** → Customer/Vendor Selection (entity picker that integrates with the order).
* **Lookup-only pages** → Entity Search + Entity 360.
* **New entity from a workflow** → Create Entity (inline or modal).
* **Order shipping/billing addresses** → Address + Select Customer Address.
* **Credit hold gating** → Customer Hold Status (with PIN override).
* **Customer-facing support cases** → Support Case (list and submit on the customer's record).
* **Module-wide PIN gates** → PIN Pad.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Transaction Components</strong></td><td>Customer Field and other entity-aware blocks for Order Forms.</td><td><a href="/pages/K8sDzAa40E6wzMLa3uDk">/pages/K8sDzAa40E6wzMLa3uDk</a></td></tr><tr><td><strong>PIN Override</strong></td><td>The full PIN-protection model across the workflow.</td><td><a href="/pages/ZB1p1C3xoZi8Tr9w4b1S">/pages/ZB1p1C3xoZi8Tr9w4b1S</a></td></tr><tr><td><strong>Roles &#x26; Permissions</strong></td><td>How entity types map to roles and workflows.</td><td><a href="/pages/90JTHrYiNFq2sGVsSqGI">/pages/90JTHrYiNFq2sGVsSqGI</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/entity-components.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.