Getting started
Klyo is a multi-tenant platform: you work inside an Organization, and your Organization is the boundary for all of its campaigns, templates, assets, and members. There is no public sign-up. You get into Klyo because someone invited you to an Organization, or because a platform admin set one up for you.
This page is the short tour. If you want the mental model first, read Core concepts.
1. You get invited
A platform admin creates your Organization and invites you by email, or an existing admin in your Organization invites you. An invite gives you a role:
- Admin: manage the Organization, its members, and its setup.
- Member: do the creative work (campaigns, templates, combination packages, assets).
- Read-only: view everything, change nothing.
See Organizations and members for how roles and invites work.
2. Log in
Sign in with your Google account. Klyo verifies your identity through Firebase, then drops you on your dashboard.
3. Land on the dashboard
The dashboard is your home base, split into two tabs. Overview carries the headline counts, the card that picks up where you left off, the setup checklist, the campaign pipeline, and the setup gaps still open across your campaigns. Activity is the running log of what has happened in your Organization: who created what, which jobs are running, and anything that failed. More on that in Activity and failures.
The campaign pipeline table sorts every creative into four stages: In Planning while it is being generated or rendered, In Review once it is rendered and waiting on sign-off, In Activation once approved and queued or pushing, and Activated once it is live on its channel.
On your first visit a short welcome tour points out the things worth knowing first: where campaigns live, the Search button, the assistant, and the setup checklist. It opens once per Organization in a browser, and you can replay it from the user menu whenever you like.
The dashboard also carries Finish setting up, the checklist of what your Organization still needs before its first campaign can run: a connected channel, a catalogue, a first campaign, and this guide. Each row ticks itself from what the console can already see, so it reads the Organization's real state rather than a list you maintain. It stays until every step is done, and the dismiss cross retires it early if you would rather not see it. Its compass button replays the tour too.
Once you have a campaign in flight, Continue where you left off appears under the counts and takes you straight back to the last builder step you had open. It is remembered on this device only, per Organization, and disappears once that campaign is gone.
4. Find your way around
The left navigation groups the work:
| Area | What you do there |
|---|---|
| Campaigns | Write the brief, choose the matrix, and walk the build steps |
| Render Queue | See every combination package on its way to a Final Video, across campaigns |
| Review | Watch each Final Video and approve, reject, or re-render it, across campaigns |
| Activation Queue | Push approved combinations to a channel or download a handoff pack, across campaigns |
| Reporting | Register the campaigns the agency built from your handoff and read their nightly KPIs |
| Catalogues | Maintain reusable creative elements and feeds |
| Templates | Browse the Creatomate templates synced into Klyo |
| Assets | Upload and organise your files |
Render Queue and Review each show a live count of what is waiting on you, and hovering an entry tells you what that area is for. The sidebar can also collapse to an icon-only rail; toggle it from the button at its bottom.
When you know what you want, skip the navigation: Search in the top bar (Ctrl/Cmd and K) jumps straight to a page, campaign, catalogue, or template. Ctrl/Cmd and J opens the assistant, and pressing ? lists every keyboard shortcut that is active where you are standing.
Your user settings, the Organization settings (profile, members, and channel connections), the welcome tour, and the System page sit in the user menu at the top right.
Platform admins also see an Admin area for onboarding and cross-org monitoring. See Administration.
5. Your first campaign
A campaign walks a step rail grouped into three phases, each step gating the next. Create plans it, Produce makes the videos, Activate ships them:
Matrix: choose the catalogues to vary, and the rules that exclude combinations.
Sample: pick one real combination to design the whole campaign against.
Brief & Idea: write the brief, generate master-story ideas from it and your sample, and pick the one every combination reuses.
Activation plan: answer where the ads run, which platform activates them, and how hosting flows; each answer reveals the next question, and the resolved target filters what comes later. A platform card locks until you connect the channel it needs.
Template: pick the one template every combination renders through, from the templates whose format your activation target accepts.
Storyboard & Ad copy: break the idea into scenes with
{{variables}}that fill in per combination, then write the campaign's ad copy.Package: bind the template's media and text fields to their sources, and pick the reference images the generation looks at. The language and voice live in Campaign settings, the gear on the campaign row and in every step header; the video model and its resolution are picked in Production on the Activation plan step.
Generate: assemble the storyboard into one video per clip of its plan and render one sample to check the template before the full run.
Render matrix: expand the matrix and render every combination through the template.
Review: watch each Final Video and approve or reject it before activation.
Publishing: set how every activated video publishes, a title that fills in per combination, the description, tags, and privacy; for a Google Ads target, also pick the ad group the release lands in (and the Demand Gen logo).
Hosting: upload approved videos to your YouTube channel ahead of the release (private until the YouTube audit clears), so activating or a handoff later reuses the upload instead of uploading again.
Activation queue: push approved combinations to YouTube, push Demand Gen ads into the picked Google Ads ad group, or hand off a Google Ads or DV360 pack.
Monitoring: see how the activated creatives performed, and which catalogue items the numbers point at. The step opens once you have activated a creative; results land once an activated video starts serving.
Walk through each step in Campaigns and Render Queue.
Where the product is today
Klyo is under active development. Some capabilities are fully wired end to end, and some are not built yet. Each page calls out plainly what works today, so you always know what you can rely on. The honest short version: planning a campaign, building the matrix, expanding combination packages, rendering them through Creatomate, reviewing each finished video, and managing templates, assets, catalogues, and feeds all work today. Every combination gets its own generated clip when a campaign's video field binds the storyboard; footage reaches a render only through that bound storyboard video, and per-scene generation on the Storyboard step produces an image preview for your eyes only. Activation works too: approved combinations push to YouTube or export as a Google Ads or DV360 handoff pack. The nightly KPI pull is built for owned YouTube uploads and Tracked Campaigns; the cross-channel roll-up over that data is the frontier still ahead. See Generation and render.
Getting help
The ? button in the top bar opens one dialog with both halves of getting unstuck. At the top, the quick ways out: ask Kai (which reads the screen you are on, so it is the fastest route to "how does this work"), open this guide, or visit digitl.com. Below, a form that reaches the Klyo team directly.
Pick what you are filing and the form asks for what that needs:
| Kind | For |
|---|---|
| Bug | Something behaved wrong. What you did, what you expected, what happened. |
| Feature | Something is missing. The job you are trying to do, and how you work around it today. |
| Support | You are stuck. What you have tried, and where the dead end is. |
You never have to say where you were: the Organization, the campaign, your name, and the screen you filed from are attached automatically. A bug or support request asks which campaign it is about; a feature request does not. Paste or pick screenshots and they go along with it. The one-line title is optional, and leaving it empty lets Klyo write one from your description.
Submitting gives you a ticket reference back. Your Organization's Support tab lists every report it has filed and where each one stands right now.
Kai can also file for you. If it cannot resolve what you are stuck on, it drafts the report and shows it to you before anything is sent, so you approve the exact words. This is the one thing a read-only member can file, since the person who hits a wall is often the one without write access.
Needs configuring
The form appears only where the Klyo team's tracker credentials are configured. Without them the dialog still shows Kai, the guide, and the digitl.com link.