Organizations and members
An Organization is the boundary around all of its data. No Organization can see another's campaigns, assets, templates, or members. This page is about running one: its profile, its people, its channel connections, and the reports it has sent us. The Organization page holds these as four tabs (Profile, Members, Connections, Support). Setting one up from scratch is a platform-admin job, covered in Administration.
What works today
Membership management, invites, roles, and the Organization profile and logo are all wired end to end. The Connections tab lists the channel connections read-only for any member (admins connect and manage them); see Channel connections. Organizations can form one-level families, where a child reads its parent's library. Archive, export, and delete are platform-admin operations, run from the admin console.
The Organization profile
Admins can rename the Organization and set its logo. The logo shows around the app, and falls back to a generated avatar when none is set. Members can view the profile; only admins can change it.
The profile also carries the Organization's brand guidelines: a free-text brand book (tone of voice, wording rules, anything every ad has to respect) that is added to every campaign's idea, storyboard, and ad copy generation automatically. Organization admins edit it right here on the profile; leave it empty and generation runs unchanged.
Members and roles
Every member has a role:
| Role | Can |
|---|---|
| Admin | Manage the Organization, its members, and its setup |
| Member | Do the creative work |
| Read only | View everything, change nothing |
Admins manage the member list:
- Invite someone by email. They get an invite email (sent best-effort, so a mail hiccup never blocks the invite itself).
- Change a member's role.
- Remove a member.
Klyo will not let you remove or demote the last admin, so an Organization can never be left with no one in charge.
Organization families
An Organization can have a parent: one level, never two. A multi-market or multi-brand client runs one parent holding the shared production library and a child per market or brand, instead of copying everything into unrelated Organizations. A platform admin sets the link up; the Profile tab shows it, and a child carries a banner naming where its inherited library comes from.
What a child inherits from its parent, read-only:
- Templates, with their versions.
- Assets, with their folder tree.
- Catalogues, with their items and linked images.
- Members. Anyone in the parent is a member of every child, at whichever role is higher, their own or the one they hold locally. The child's member list shows them, and they count toward the last-admin guarantee, so a child staffed entirely from the parent is fine.
Inherited rows are usable but never editable from the child: bind an inherited template to a campaign, pin an inherited asset, select an inherited catalogue item, but edit any of them in the parent. Inheritance runs one way only. A parent sees nothing of its children's work, and siblings see nothing of each other's.
Brand guidelines are the one part you choose. A per-child switch, off by default, prepends the parent's brand book to the child's own so both apply. Every other setting stays the child's: its credits, its Google Cloud data plane, its Activation Profiles, and its own campaigns.
Connections do not inherit wholesale. A parent grants one connection to one child at a time; see Sharing a connection.
Parent members get a Group page: one row per child with its campaign counts by phase, and the group totals above them, so a holding company reads every market at once without switching Organizations. The totals sum only the children whose read succeeded, so a child that failed to load is missing from them rather than counted as empty.
Detaching a child is refused while campaigns in that child still use the parent's templates, assets, or catalogues. Rebind or copy what they use first.
Support
The Support tab lists every report this Organization has sent the Klyo team, with the status our tracker holds right now. Klyo keeps no copy of a ticket, so what you see is always current rather than a snapshot. Filing one is done from the help button in the top bar; see Getting help.
Switching Organizations
If you belong to more than one Organization, you switch between them from your account. Each switch changes which Organization's data you are looking at, everywhere in the app.
Archive, export, delete
These are platform-admin actions, run from the admin organizations console (see Administration):
- Archive an Organization to make it read-only without losing anything. Unarchive to bring it back.
- Export a full JSON snapshot of the Organization's Klyo-side data (the file bytes in storage are not included).
- Delete an Organization permanently, which unwinds its Klyo-side data.
What you can do today
- Manage members: invite by email, change roles, remove.
- Keep the last-admin guarantee.
- Set the Organization name and logo.
- Switch between the Organizations you belong to.
- Read a parent's templates, assets, catalogues, and member list from a child.
- (Parent member) read every child's progress on the Group page.
- Track the reports your Organization has filed on the Support tab.
- (Platform admin) archive, unarchive, export, and delete an Organization.