Workspaces and scope

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

UseNadia has 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.

What a workspace is

A workspace is a folder of channels: Vincent holds his Instagram and TikTok accounts; Restaurant holds the restaurant’s.

• Every channel is in exactly one workspace. No channel sits outside a workspace, and none sits in two at once.
• Every organization has at least one workspace. The first one, created for you, carries the organization’s name; you can rename it.
• A channel you connect goes into the workspace of the current scope (or, if there is none, the first one).

As long as you have a single workspace, there is nothing to do: all your channels are in it.

The three kinds of scope

Scope	What it is	What pages show
A workspace	A folder of channels	Every channel in the workspace
A channel	One account	That account only
All channels	Everything in the organization	An overview across all of it

The switcher lists your workspaces, each one expanding to its channels with a chevron. All channels only appears from two workspaces on: with a single one, it would say the same thing as that workspace.

The scope is kept in a cookie and survives a reload. When nothing has been chosen yet, or the stored workspace no longer exists, UseNadia falls back to the first workspace; never to All by default, because “everything at once” is nobody’s working context.

Creating and organizing workspaces

1. Create a workspace

   Account switcher, Create a workspace at the bottom of the list, or Settings, Workspaces, New workspace: the same form opens. Only the name is required.

2. Put channels in it

   Settings, Workspaces (or Manage workspaces… in the account switcher). On a channel’s row, pick its workspace (Workspace of this channel): the channel moves, it leaves its former workspace.

3. Edit or delete

   Each workspace has its card there: the gear reopens the form, the bin deletes it. Deleting a workspace disconnects nothing: its channels move to the first workspace. The last workspace of an organization cannot be deleted.

The context of a workspace

The form of a workspace goes beyond its name: logo, website, time zone (the Detect button takes your browser’s), country, type (personal, business or client) and About, a free text of up to 2,000 characters.

This context is for the agent. Before writing a post, a reply or a DM for one of the workspace’s channels, it reads it (the MCP tool workspaceList returns it): language and tone follow the country and the audience, times are understood in the workspace’s time zone. In About, describe the brand, the audience and the tone, as you would for someone taking over your accounts tomorrow. A field left empty says nothing, and the agent does not make it up.

The logo replaces the workspace’s icon in the account switcher and in the list of workspaces.

Time zone

A workspace’s time zone is your audience’s time. The calendar, the composer, the time slots and the analytics show in the time zone of the scope’s workspace (the chosen channel’s, or the first workspace when the scope is “All”). Scheduled at 18:00 for a workspace in Malta, a post stays at 18:00 on the whole team’s screen, even when you work from Bangkok: top right of the calendar, next to the time zone, a reminder then says how far your browser is (“your browser is at +6 h”). Clicking the time zone opens the workspace’s form.

A post keeps its instant. Changing a workspace’s time zone moves no post: only the way it is shown changes. A workspace without a time zone shows in your browser’s, as before.

The agent follows the same rule: “at 6 pm” means 18:00 in the time zone of the workspace of the channel it is for.

How many workspaces each plan includes

Plan	Workspaces
Solo	1
Team	3
Agency	10

At the limit, Create a workspace says so (“1 workspaces out of 1”, for instance) and See the plans takes you to Settings, Subscription, where you can move to the plan above. Existing workspaces are untouched: only the next one is refused.

What the scope drives

Page	What the scope does
Calendar	Filters channels and posts (/posts?integration= for a channel, &group= for a workspace)
Contents	Shows the cards aimed at a channel in scope, or at no channel
Composer	Pre-checks the workspace’s channels, but still lists all of them, see below
Inbox	Shows the Instagram channels in scope, and only those
Analytics	Picks the channel to analyse from the scope
Agent	Sends the channels in scope as working context

The composer is the exception

The composer’s channel picker lists every channel in the organization, not only the ones in scope. Sending one video to three Instagram accounts and two TikTok accounts in one go is the normal case here, and having to switch workspace mid-draft to do it would be absurd.

The scope only decides what is pre-checked when the composer opens. The All channels scope checks nothing.

Analytics can only show one channel

An analytics page is about one account. In a workspace scope, it takes the first compatible channel and offers, next to the channel name, a local, unsaved picker. Reload the page and you are back to what the sidebar says.

To pin a channel everywhere and for good, select it in the account switcher instead, under its workspace.

When a page needs a capability the scope has not got

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

The menu never changes with the scope: an entry the current workspace cannot serve is greyed out, with a tooltip saying why, and stays clickable. Opening it takes the scope to where the capability is instead of asking you:

• when the destination is not in doubt (the workspace you are already in, or the only workspace with that kind of channel), it switches, with a notification saying so, since the sidebar just moved on its own;
• when two workspaces could answer, the empty screen offers them as buttons;
• when nobody has connected the platform, it stops on a discovery message and an Add a channel button.

The switch happens once per page, and never after a choice made by hand in the switcher: otherwise the switcher would become unusable on that page.

Caution

That 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 workspace away.

Workspaces, the Public API and the MCP

• GET /public/v1/workspaces lists your workspaces, each with the ids of its channels and its context; GET /public/v1/integrations?workspace=<id> only lists the channels of one workspace, and every channel carries its workspace. See Channels.
• On the agent side, the MCP tool workspaceList does the same, and integrationList takes a workspace parameter.

Note

GET /public/v1/groups, the ?group= filter and a channel’s customer field stay, deprecated, for the SDKs already published: they now return the workspaces. Write workspaces and workspace in any new code.