Skip to content

How UseNadia works

UseNadia has a small vocabulary that the rest of these docs and the API both assume. This page defines it once.

Everything you own lives inside an organisation: channels, brands, posts, media, content cards, tags, automations, team members and settings. You can belong to more than one, and when you do, an organisation switcher appears in the top bar. Switching reloads the app into that organisation’s data.

The first person to register creates the organisation and becomes its owner. Others join by invitation, see Team.

A channel is one connected account: one Instagram account, one TikTok account or one YouTube channel. Connecting the same platform twice gives you two channels.

Channels can be disabled rather than deleted, from Manage brands & channels. A disabled channel keeps its history and stops being available for posting. The same modal can also delete a channel, which erases what UseNadia stored from the platform — see Manage a channel.

YouTube is a special case: a YouTube channel connects, reports analytics and can be targeted by content cards, but publishing to it waits for Google’s API audit. See Posting rules by platform.

A brand is a named group of channels — “Vincent” being his Instagram accounts and his TikTok accounts. It is the working context: picking a brand in the account switcher points the calendar, the inbox and analytics at that brand’s channels.

A channel can belong to several brands at once, which is what makes brands different from the original project’s Customer. The model and the API still call them AccountGroup; only the interface says “brand”.

See Brands and scope.

The scope is what the account switcher currently points at: one channel, one brand, or All channels. It is stored in a cookie and it drives every page — there is no second channel picker anywhere in the app.

When a page needs a capability the current scope does not have (the Inbox needs Instagram, Analytics needs Instagram, TikTok or YouTube), the page moves the scope to where the capability is and tells you it did, rather than asking.

A content card is a video before it is a post: an idea, then a script, then something to shoot, edit and schedule. Cards live on the Content board, a pipeline of seven columns — Idea, Script, Validated, To shoot, To edit, To schedule, Published — and move between them by drag and drop. A card holds what the stage needs: notes and tags, a hook and a script, the channels it targets, a planned date, the final video, and the resource the video promises.

Schedule on a card opens the composer pre-filled — channels ticked, script as the caption, final video attached, planned date or the next free slot — and the card then follows its post: it shows the scheduled date, moves to Published on its own when the post goes out, and displays the post’s performance afterwards. A card can carry several posts, one line per channel.

The board follows the scope: a card appears when it targets a channel of the scope, or no channel at all.

When you schedule one piece of content to five channels, UseNadia stores five posts that share a group. That is why the API has both deletePost and deletePostsFromGroup, and why deleting from the calendar removes the whole set by default.

Inside a single post you can have multiple parts. On Instagram, part one is the post and the rest are comments on it. TikTok and YouTube take the first part only. See Threads and comments.

By default you write once in the Global tab and every selected channel gets the same text. Unlocking a channel’s own tab detaches it, so you can rewrite that version without touching the others — the usual reason being a character limit that differs per platform, see Writing the post.

Each platform has its own settings: an Instagram post type and collaborators, a TikTok privacy level and posting method, a YouTube title and visibility. They appear at the bottom of the composer, and in the API as a settings object with a __type naming the platform. Some are required and the post will not save without them.

When several channels of the same platform are selected, the composer shows one settings block for all of them and copies what you type across, because these settings describe the post rather than a resource owned by one account.

A tag is a coloured label on a post. The colour is what the post card shows on the calendar, which makes tags the practical way to see campaign or content type at a glance.

An automation answers a comment or a story reply with a direct message — typically a resource (a link, a guide, a checklist) promised in exchange for an email address. It is a template, drawn once on Automations as a tree of steps, and posed on as many publications as you like, each pose with its own trigger words and values. A matching word triggers a public reply and a direct message, the message asks for an email, and the address gets the resource. The people who went through, with their emails, are listed per pose and exported as CSV.

See Comment → DM automations.

Each channel has a list of time slots, the times of day it normally posts. Slots drive the rows in the calendar’s Day view and the find-slot API endpoint, which is what Create Post uses to offer you a free slot. They are a scheduling convenience, not a restriction: you can always post at a time that is not a slot. See Posting time slots.

State Meaning
Draft On the calendar, never publishes. Prefixed Draft: on the card
Scheduled Queued for its date. This is the normal state
Published Sent to the platform. The card links to the live post
Error The platform rejected it. Red ! badge, reason in the tooltip
Sent, unconfirmed Sent, but the platform never confirmed it. Amber ? badge

Every post has a public preview page at /p/:id. Sharing that link lets someone read the post as it will appear without an account; leaving a comment on it requires logging in to UseNadia. See Share a post for approval.

A set is a saved selection of channels and their settings. A signature is a block of content appended to posts; one signature can be marked auto-add and is then inserted into every new post. Both are managed in Settings, see Sets and signatures.