> For the complete documentation index, see [llms.txt](https://acoservice.gitbook.io/acoservice-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://acoservice.gitbook.io/acoservice-documentation/for-platform-operators/creating-a-tenant.md). # Attaching an owner to a tenant Operators do not create tenants. This page covers the one thing they do, attaching an owner to a tenant that has none. Operators do not create tenants. Owners do, in the [owner console](/acoservice-documentation/running-your-aco/creating-your-aco.md) at `acoservice.app/owner`. Give it a name and an address, and the ACO exists. The seven-step wizard this page used to describe was removed in ACO-22. ## When an operator does act Some tenants exist with no owner attached: the legacy tenants from before self-serve, or one created on someone's behalf. For those, an operator opens `/platform/tenants/` and the **Owner** tab. ## The Owner tab Not attached, the tab shows a picker over every owner account. Each option is the owner's name, or their email if they have no name, with "(no Discord yet)" marked next to any account with no linked Discord id. Pick one and press **Attach**. Attaching makes the owner's linked Discord id a tenant admin with the owner role. An owner with no Discord id can still be attached, for billing, but cannot manage the ACO until they link one. The tab says so. An owner whose subscription is closed or lapsed gets a warning line: > This owner's subscription is closed. A published ACO attached here is taken offline by the next billing sweep. > This owner's subscription has lapsed. The grace period is running and the sweep will close the ACO when it ends. Attached, the tab shows the owner's name, email, Discord id and subscription state, and a **Detach** button. Detaching stops billing under that owner and leaves their tenant-admin access in place until an operator removes it on the Admins tab. Detaching a closed ACO clears the closure mark; it stays unpublished until someone publishes it. {% hint style="info" %} Attaching a live ACO to an owner whose subscription is closed takes it offline at the next hourly sweep, and the owner gets the usual closure message; detaching a closed ACO clears the closure mark and leaves it unpublished until someone publishes it. {% endhint %} ## Related * [Provisioning a tenant bot](/acoservice-documentation/for-platform-operators/provisioning-a-bot.md) * [The setup status checklist](/acoservice-documentation/for-platform-operators/setup-status.md) * [Managing tenants](/acoservice-documentation/for-platform-operators/managing-tenants.md) --- # 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://acoservice.gitbook.io/acoservice-documentation/for-platform-operators/creating-a-tenant.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.