> 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/running-your-aco/owners.md).

# The owner console

The owner console — where you set up and run your ACO yourself.

If you run an ACO on this platform, **acoservice.app/owner** is your console. You create your ACO there, brand it, preview it privately, and take it live — without anyone at ACO Service touching it.

This section is for **owners**. Two other audiences have their own sections and it is worth knowing which you are:

| You are…                                         | Where you work                    | Section                                                                    |
| ------------------------------------------------ | --------------------------------- | -------------------------------------------------------------------------- |
| **An owner** — you run an ACO                    | `acoservice.app/owner`            | This one                                                                   |
| **A tenant admin** — you help run one day-to-day | `<your-aco>.acoservice.app/admin` | [For Tenant Admins](/acoservice-documentation/for-tenant-admins/admins.md) |
| **A member** — you buy through an ACO            | that ACO's own site               | [For Members](/acoservice-documentation/for-members/dashboard.md)          |

An owner is usually also an admin of their own ACO. The console is where you handle the *business*: creating it, branding it, publishing it, paying for it. The admin console is where you run it *daily*: customers, tabs, invoices, orders.

## The one rule worth knowing up front

**Nothing is behind a paywall except publishing.**

You can create an ACO, brand it, connect Discord, set up your content, and preview the whole thing on its real address without a subscription. You can also subscribe on day one and build a month later. There is no order you have to do things in and no step that blocks another.

The only thing a subscription buys is the ability to make your site **public**.

It is **$100 a month**, one plan, unlimited published ACOs — see [Subscription](/acoservice-documentation/running-your-aco/subscription.md).

## What you do here

1. [Sign in](/acoservice-documentation/running-your-aco/signing-in.md) with ResiFactory and connect your Discord account.
2. [Create your ACO](/acoservice-documentation/running-your-aco/creating-your-aco.md) — a name and an address.
3. [Brand it](/acoservice-documentation/running-your-aco/branding.md) — colours, logo, wording.
4. [Add a domain](/acoservice-documentation/setting-up-your-tenant/custom-domain.md): the console's Domains page lists your addresses, checks DNS, and makes one primary.
5. [Preview it](/acoservice-documentation/running-your-aco/preview-and-publish.md) — privately, on its real address.
6. [Subscribe](/acoservice-documentation/running-your-aco/subscription.md) — whenever you like.
7. [Publish](/acoservice-documentation/running-your-aco/preview-and-publish.md#publishing) — when both are ready.

Every ACO in the console has an **Open admin console** link that takes you to that ACO's own admin console (a second sign-in with Discord, because the admin console lives on the ACO's address).

## Where to get help

The [operator Discord](/acoservice-documentation/community/community.md) is the fastest route — it is other people running the same kind of business, plus staff. Connect your Discord in the console and you are let into the operator channels automatically.


---

# 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/running-your-aco/owners.md?ask=<question>&goal=<user_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.