Brands and scope

Where: the account switcher, at the top of the sidebar

UseNadia has exactly one place where you choose what you are working on. Not a filter on the calendar, another on analytics and a third on the inbox — one switcher, and every page follows it. That choice is the scope.

The three kinds of scope

Scope	What it means	What the pages show
A brand	A named group of channels	Every channel of the brand
One channel	A single account	That account only
All channels	Everything in the organisation	A control view over the lot

The switcher lists them in that order: your brands first, each unfolding into its channels with a chevron; then Not in a brand (or Channels if you have no brands at all), where each loose channel is selectable like a brand of one; then All channels.

The scope is stored in a cookie and survives a reload. When nothing has been chosen yet, or the remembered brand no longer exists, UseNadia falls back to the first brand, failing that the first channel, and only then to All — never to All by default, because “everything at once” is nobody’s working context.

What a brand is

A brand is a named group of channels you work on together: Vincent being his Instagram accounts and his TikTok accounts.

The one thing that matters about brands: a channel can be in several at once. That is the difference from the original project’s Customer, which is exclusive — one channel, one customer. Overlapping groups let a channel be both Vincent and Everything in French without duplicating it.

Note

The database model and the API still call them AccountGroup. Only the interface says “brand”.

Creating and editing brands

1. Open the modal

   Account switcher, Manage brands & channels.

2. Create

   Type a name in New brand name, then Create brand (POST /account-groups).

3. Choose its channels

   Tick the channels that belong to it, then Save (PUT /account-groups/:id). Ticking a channel that already belongs to another brand is fine and expected.

4. Rename or delete

   Both are in the same row. Delete brand removes the grouping only — the channels stay connected and fall back into Not in a brand.

What the scope drives

Page	What the scope does
Calendar	Filters channels and posts (/posts?integration= on a channel, &group= on a brand)
Content	Shows the cards that target a channel of the scope, or no channel at all
Composer	Pre-ticks the brand’s channels — but still lists all of them, see below
Inbox	Shows the Instagram channels of the scope, and only those
Analytics	Picks the analysed channel from the scope
Agent	Sends the scope’s channels as the context it works on

The composer is the exception

The channel selector inside the composer lists every channel of the organisation, not just the scope’s. Sending one video to three Instagram accounts and two TikTok accounts in a single pass is the normal case here, and having to change brands mid-composition to do it would be absurd.

The scope only decides what is pre-ticked when the composer opens. Scope All channels pre-ticks nothing.

Analytics can only show one channel

An analytics page is about one account. In a brand scope it takes the first capable channel and offers a local, non-persisted select next to the channel’s name. Reload the page and you are back to what the sidebar says.

To pin a channel everywhere and durably, select it in the switcher under its brand instead.

When a page needs a capability the scope has not got

The Inbox needs Instagram. Analytics needs Instagram, TikTok or YouTube.

The menu never moves with the scope: an entry the current brand cannot serve is dimmed, with a tooltip saying why, and stays clickable. Opening it takes the scope to where the capability is rather than asking:

• when the destination is unambiguous — the brand you are already in, or the only brand that has the channel — it switches, with a toast saying so, because the sidebar just moved on its own;
• when two brands could answer, the empty state offers them as buttons;
• when nobody has connected the platform at all, it stops on a discovery message and an Add Channel button.

The switch happens once per page, and never after you have made a choice by hand in the switcher — otherwise the selector would be unusable on that page.

Caution

This is why a page can change your sidebar. It is not a bug: it is the app refusing to show you an empty screen when the answer is one brand away.

Brands and the Public API

Brands are on the app’s own API, at /account-groups, which authenticates with your session rather than an API key.

Caution

GET /public/v1/groups does not return brands. It returns the original project’s Customer records, which UseNadia no longer writes to from the interface — so here it is almost always empty. The same goes for the group filter on GET /public/v1/integrations. See List groups.