# Getting Started


An Omumu site is yours from the first minute: your own address, your own students, your
own money. This chapter is the first hour — what the sign-up hands you, the handful of
settings that make the site yours rather than a template, how money and email get
connected, and where to look when something says it needs a different plan. It is the
only chapter with almost no conversational path: setting up a business is paperwork, and
most of these pages have no agent tools. The one exception, your brand, has them.

A path such as *Settings → Business Details* names a group in the admin's navigation —
the rail on the left on a laptop, behind the Menu button on a phone — and the page under
it.

## Concepts

**A site and its Headmaster.** Everything on Omumu belongs to a site: courses, pages,
offers, people. You, the person who created it, are its Headmaster — the role that can
change anything on it. Other people on your site are students, or staff you invite to work
with students. Which site you are on is always visible in the address; signing in to your
site is separate from any account you may hold on omumu.com.

**The admin and its home.** Every admin page shares one navigation: Home and five groups —
Products, Customers, Sales and marketing, Integrations and Settings. Home is a status page. Its
first card, *Set up your site*, is a checklist computed from what is actually true on the
site, not from what you have clicked: edit your front page, take payments, connect email,
add your first course, create your first offer, connect your AI. Items tick themselves
when the thing is done, and the card can be dismissed.

**What works before you connect anything.** Sign-in links, receipts and the email a
person gets when they are given access to a course always go out through Omumu. Invoice
requests work without a payment provider. Everything else that leaves the site in your
name — card and Vipps payments, email sequences — needs a connection you make once, and
the pages for those connections say whether they are connected.

**Your plan decides some doors.** A site runs on a plan. The plan decides which features
the admin offers and the limits on storage, courses and people; a page the plan does not
include says so and points you to Omumu rather than erroring. How you reach Omumu support
is part of the plan too — email support on most plans, priority email on the higher
ones, phone support on the top one. This manual does not list plan names or prices: they are being consolidated, and
*Settings → Platform Subscription* always shows yours.

## Hands-on

### Create your site

Mira starts at omumu.com's *Create your sales machine* page. Step one asks for her email
and her name; step two asks for a card, with nothing charged today — the card is so the
site keeps running after the fourteen-day trial, at the trial plan's monthly price in
Norwegian kroner. She lands signed in on her new site's Home, with the setup checklist
waiting. A welcome email tells her the site is ready and how to sign in again.

A second door exists for people who come through a partner: a voucher that creates the
site on a different starting plan. Either way the site, the checklist and this chapter
are the same.

There is no agent path to creating a site.

### Tell the site who you are

*Settings → Business Details* holds the words the platform uses in your name: the site's
name and description, the sender address on emails to your users, the support address
shown to students, the address invoice requests go to, and the site's language (English,
Norwegian, or whatever the visitor's browser asks for). The *Legal* tab takes your short
and full company name and organisation number; the *Address* tab your street address.
These appear on receipts and legal pages, so fill them before you sell. The page also
shows your plan's storage limits and what you have used.

These settings have no agent tools; this is admin work.

### Make it look like you

Mira says: *"Set my brand: primary colour #1F4E79, accent #F2A900, the Sora font, and
rounder corners."*

`omumu_brand_update` merges those choices into the site's brand *draft*; `omumu_brand_get`
returns the draft and the published brand, the derived light and dark colour roles, and
the editor's address. The draft is not live: your pages keep the published brand until you
publish on the Branding page. In the admin, *Settings → Business Details → Branding* shows
a live preview — a course card and a lesson in your colours and font — with pickers for
primary and accent colour, a catalogue of fonts in four families, corner roundness, and
uploads for a logo mark and a logo type, each with an optional version for dark
backgrounds. *Save draft*, look at the preview, then publish. Until you publish, the site
wears Omumu's defaults.

### Get paid

*Settings → Payment Processors* shows Stripe and Vipps, each marked connected or not. Stripe
connects through a single *Connect* button that opens Stripe's own onboarding; Vipps takes
the four credentials from your Vipps merchant portal — client id, client secret,
subscription key and merchant serial number. Invoice requests work with neither. The
Selling chapter is about what you sell once a provider is connected.

### Send email in your own name

*Settings → Email Integration* shows Resend (recommended) and SendGrid, each marked set up
or not. Resend asks for your domain and a region and gives you DNS records to add at your
domain host; once they verify, sequence emails leave from your domain. Until then,
sequences hold their emails rather than sending them, and the pages that feed sequences
say so. Sign-in links and receipts never wait on this.

### Connect your AI

*Integrations → Set up your AI assistant* is the page that connects Claude, ChatGPT, Cursor,
VS Code or a terminal to your site and shows a green "Connected" the moment one of them
talks to it. Once connected, the assistant's first calls are `omumu_site_context` — which
site it is on, your role there, the features the plan enables — and `omumu_profile_get`,
which names the connection after you and the site. The Agent Surface chapter covers the
connection, keys and consent in full; the setup checklist's last item is this page.

### Bring in your team

*Customers → Users → Create user* adds a person by name and email with a role — student,
staff or Headmaster — and optionally a course to give them at once. Omumu emails them a
link to sign in; there is no password to hand over. Staff see the admin groups their role
allows; a second Headmaster sees everything you do.

### Your plan and billing

*Settings → Platform Subscription* shows your plan, renewal and next billing date, the
card Omumu charges, your invoices, and *Compare Plans*. Cancelling returns the site to the
free plan at the end of the paid period; you do not lose the site.

### What to know about the edges

Stated plainly: the *Support* link in the admin header mails your own site's support
address — that is the right address for your students, and the wrong one for you; reach
Omumu through the channel your plan gives you. *Account → Billing* in the header is you as
a customer of your own site, so it is empty on a new site; your Omumu card and invoices
are under *Settings → Platform Subscription*. And plan names, prices and the comparison
page are in flux, so trust the subscription page over anything printed.

## Reference

### `omumu_brand_get`

Gets the site's Brand: the published choices and revision the site wears, the draft choices and whether they differ from published, the draft's derived light and dark color roles and any contrast adjustments, the font catalog identifiers and roundness steps to choose from, and the admin editor URL. Publishing is a human step: the creator publishes the draft in admin at editorUrl.

- **Write category:** read-only
- **Access:** requires the `BRAND_READ` permission

No parameters.

### `omumu_brand_update`

Merges any of the given choices into the site's Brand draft; choices left out stay as they are, and an invalid color, unknown font or logo that is not this site's refuses the whole update. Returns the Brand as omumu_brand_get does. The draft is not live: the Site's pages and its public Brand JSON keep the published Brand until the creator reviews the draft and publishes it themselves in admin, at the returned editorUrl. There is no tool to publish.

- **Write category:** standard write
- **Access:** requires the `BRAND_WRITE` permission

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `accentColor` | string | no | The accent color as #rrggbb. Becomes the tertiary role. |
| `font` | string | no | A font identifier from the catalog that omumu_brand_get lists under fonts, e.g. raleway. |
| `markDarkResourceId` | string | no | Id of an image already uploaded to this site (omumu_resource_upload_presign) to use as the logo mark for dark surfaces (square, at least 1024 px). It is checked like an upload in the Brand editor. |
| `markResourceId` | string | no | Id of an image already uploaded to this site (omumu_resource_upload_presign) to use as the logo mark (square, at least 1024 px). It is checked like an upload in the Brand editor. |
| `primaryColor` | string | no | The primary color as #rrggbb, e.g. #215fa6. Kept exactly wherever it can carry readable text; otherwise nudged just enough to pass contrast, reported under adjustments. |
| `roundness` | string | no | Corner style: sharp, soft or round. |
| `typeDarkResourceId` | string | no | Id of an image already uploaded to this site (omumu_resource_upload_presign) to use as the logo type for dark surfaces (wide, at least 400 px wide). It is checked like an upload in the Brand editor. |
| `typeResourceId` | string | no | Id of an image already uploaded to this site (omumu_resource_upload_presign) to use as the logo type (wide, at least 400 px wide). It is checked like an upload in the Brand editor. |