> For the complete documentation index, see [llms.txt](https://functor.gitbook.io/functor-network-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://functor.gitbook.io/functor-network-docs/use-cases/enterprise-integration.md).

# Enterprise Integration

Enterprise operations onchain require mechanisms for fine-grained **control** and policy enforcement that go beyond standard multi-signature wallets. Functor's architecture introduces a set of technical primitives designed to enable such operations with a high degree of **customization** and verifiable **security**.

The technology makes it possible to define dynamic, policy-driven workflows, offering a more flexible alternative to rigid, hard-coded smart contract logic for managing team-based assets and operations.

### **Programmable Policy Control**

Functor enables **programmable policies** to be layered on top of accounts. This allows for the **customization** of operational workflows. 

*For example, policies can define specific rules like spending limits, required signers based on transaction size, or whitelisted counterparties.*

### **Onchain Verification for Security and Trust**

**Security** is rooted in **onchain verification**. All policies are enforced directly by the network, which minimizes reliance on off-chain components or trusted third parties. 

This creates a transparent environment where the rules governing an account are auditable and their execution is guaranteed by the protocol, establishing **trust** in the system’s integrity.

### **Foundations for Institutional Workflows**

These technical primitives - programmable policies, onchain verification, and flexible signer logic - form the building blocks for **institutional-grade** infrastructure. They make it possible to construct decentralized treasury management systems and other complex financial workflows within a self-custodial framework.