> For the complete documentation index, see [llms.txt](https://taas-docs.stokr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taas-docs.stokr.io/asset-distribution/distribution-delegation.md).
# Distribution delegation
Tokenization, like traditional securitization, involves multiple transaction parties who may be subsidiaries, departments within larger organizations, or separate contractual entities.
Our platform's API structure and granular permissions system (see [Users and Roles](/api-overview/users-and-roles.md)) enable you to delegate specific duties within the distribution workflow.
## Delegation of complete distribution flow
You can delegate the entire distribution process to a third party while maintaining oversight and control.
**Example scenario:** An asset manager contracts with STOKR and wants to delegate distribution to a specialized distributor.
The asset manager, as the primary customer, can orchestrate integration through two approaches:
* **Proxy service approach** - Build a proxy service that interfaces with STOKR, allowing the distributor to integrate with your proxy while maintaining separate user records for detailed audit trails and permission controls.
* **Direct access approach** - Create dedicated users for the distributor's employees and systems, allowing them direct interaction with the STOKR platform while reducing your development overhead.
In this model, users have role-based permissions: asset manager employees access issuer/asset/whitelist operations, while distributor staff access investor/wallet/investment operations.
## **Event-based integration with third parties**
You can set up webhook events that automatically notify third-party providers to handle specific tasks:
* **Investor created** - Trigger KYC processes with compliance providers
* **Wallet added** - Initiate ownership verification with wallet verification services (e.g., for travel rule compliance)
* **Investment created** - Generate invoices and collect payments through payment processors
These are typically three separate providers, each specializing in their respective area: KYC providers for compliance verification, wallet verification providers for ownership confirmation and regulatory requirements like travel rule, and payment processors for invoicing and payment collection.
This approach enables you to outsource specific processes while maintaining overall workflow coordination.
## **Maintaining final authority**
Even when outsourcing distribution processes, you can retain control over critical decision points to ensure final authority over key actions:
* **Verification oversight** - Keep investor and wallet verification within your compliance team while delegating other distribution tasks
* **Distribution approval** - Maintain control over final distribution triggers (such as end-of-offering distributions) while allowing third parties to handle day-to-day subscription processing
This structure ensures you benefit from third-party expertise while preserving decision-making authority over the most critical aspects of your offering.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://taas-docs.stokr.io/asset-distribution/distribution-delegation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.