> For the complete documentation index, see [llms.txt](https://docs.creditcoop.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creditcoop.xyz/core-concepts/the-spigot/spigot-roles.md). # Spigot Roles Four parties interact with a Spigot. Two are Spigot-native roles; two are inherited from the Line of Credit that owns it. ### Owner The Line of Credit contract itself. The Owner is the Spigot's **default beneficiary**: escrowed revenue not allocated to third-party beneficiaries accrues to the Owner and is used to repay the facility's Credit Positions. Ownership of the Spigot transfers to the Line at deployment and the transfer is one-way while the facility is live. ### Operator The Borrower-side role. * Claims revenue from Revenue Contracts into the Spigot (splitting it per the agreed terms) * Calls whitelisted business-as-usual functions on Revenue Contracts — never claim or ownership-transfer functions * Claims the Borrower's (non-escrowed) share of revenue * Receives ownership of Revenue Contracts back when they are removed after repayment * Can update the Operator address while the facility is healthy; if the facility is LIQUIDATABLE, the Admin can update it ### Admin & Servicer (inherited from the Line) The Line's Admin and Servicer roles act on the Spigot for configuration and servicing: * Admin/Servicer: add Revenue Contracts, update whitelisted functions, execute DEX trades of escrowed revenue, manage beneficiary configuration, recover tokens in emergency states * Servicer: claim revenue, apply beneficiary repayments, sweep balances on repayment * Borrower + Admin jointly: reset beneficiaries and update splits when no debt is outstanding; the OTC Swap Servicer consents (with the counterparty) to OTC swaps See [Roles & Permissions](/core-concepts/secured-line-of-credit/secured-line-of-credit/roles-and-permissions.md) for the full facility role model. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.creditcoop.xyz/core-concepts/the-spigot/spigot-roles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.