Workspace & Projects
The workspace is your global workspace. It contains all of your projects (brands), each isolated with its own brand identity, social channels, and analytics.
Workspace
One workspace per user account. Contains all your projects. Linked to a pricing plan.
Project
Represents a brand or client. Each project has its own brand identity, social accounts, content, library, settings and automations.
Active Project
Only one project is active at a time. The project switcher (logo top-left of the app) allows you to toggle between projects. The active project defines the context for all operations.
Video tutorial coming soon
Creating a project & switching between them
| Section | Role | Configuration |
|---|---|---|
| Dashboard | Active project overview | Automatic |
| Vibe | Conversational AI brain: chat, generate, publish, ask anything | None |
| Studio | Flyer, Brand Guide and video generation | Brand identity required |
| Library | All generated & uploaded media in one place | Automatic |
| Automations | Recurring workflows (Monday morning, etc.) | Manual configuration |
| Inbox | Incoming comments and DMs + auto-reply | Webhook + OAuth |
| Posts | Draft and published content list | Automatic |
| Schedule | Publish queue and calendar | Social accounts required |
| Editorial | Tone of voice, content pillars, hashtags | Manual configuration |
| Campaigns | Email & SMS campaigns | Provider configured |
| Analytics | Performance statistics | Automatic snapshots |
| Marketplace | Discover and hire creators | None |
| Settings | Brand identity, social accounts, Turbo, billing | Mandatory onboarding |
Invite an Admin or an Editor
Team is managed at the workspace level, from the Team tab on the Projects page (not inside a single project's Settings). Every seat you invite draws from one shared, account-wide pool.
Owner
The account creator. Always has full access to every project, can't be removed or reassigned a role.
Admin (account-wide)
Full operational access to every project the owner has, present and future. Invited once from the Team tab; no per-project scoping needed. Two owner-only actions stay off-limits: an Admin cannot DELETE or TRANSFER a project — the project Settings "Danger" tab is hidden for them — and can never touch the owner's billing or account.
Editor (per-project)
Full access to exactly one project, chosen at invitation time — create and manage its content, automations, brand and editorial. Access is segmented by scope: three are granted by default (content, automations, editorial); two are opt-in and sensitive (publish & connect accounts, private inbox), toggled with checkboxes at invite time. If the Editor already has their own account, the shared project appears in their own workspace with a "from workspace X · Editor" badge; all work draws from the inviting owner's credit pool, and the owner's private usage/credit figures stay hidden from them.
| Detail | How it works |
|---|---|
| Seat pool | One shared cap per account: the owner counts as the first seat, then every distinct Admin or Editor (active or pending) counts as one more, regardless of how many projects they touch. |
| Extra seats | Run out of seats on your plan? Buy more anytime from the Marketplace — no plan upgrade required. |
| Invitation | Set a name, a role, and — for Editor — the one project they're scoped to plus the permission scopes to grant. An email invite is sent; clicking it creates their account and grants access immediately. |
| Permission scopes | An Editor's access is segmented: content, automations and editorial are granted by default; publishing/connecting accounts and the private inbox are opt-in checkboxes (they expose OAuth tokens and DMs). The owner or an Admin manages them. Each scope also carries its read surfaces: the project's Analytics follow the content scope, the automation approval queue follows automations, and the Inbox auto-reply knowledge base follows inbox. |
| Shared billing | Everything a member generates on a project is billed to and capped by the project OWNER's credit pool — not the member's own account. Attribution is kept per action. |
| Traceability | The Team tab shows each member's monthly credit total (with a colour), a per-member credit history down to each generated asset, and an Activity log of sensitive non-credit actions (renames, brand config, member changes). These figures are visible to the owner and Admins only. |
| Owner-only actions | Deleting or transferring a project, and managing billing / the account, are reserved for the project owner. Neither an invited Admin nor an Editor can delete or transfer a project (enforced both in the UI and server-side); the Settings "Danger" tab only appears for the owner. |
| Managing a member | Resend a pending invite, adjust scopes, or remove access from the action menu on their row. The Owner row has no action menu. |
| Feature | Free | Starter | Pro | Agency | Enterprise |
|---|---|---|---|---|---|
| Projects | 1 | 3 | 10 | 30 | ∞ |
| Social Accounts | 1 | 5 | 20 | ∞ | ∞ |
| Generations/month | 3 | 25 | 100 | 500 | ∞ |
| Auto-replies/month | 0 | 50 | 200 | 500 | ∞ |
| Automations | 0 | 3 | 10 | 30 | ∞ |
| Team seats | 1 | 1 | 2 | 5 | ∞ |
| Turbo flows / project | 1 | 1 | 2 | 5 | ∞ |
| API Access | ❌ | ❌ | ✅ | ✅ | ✅ |
| White-label | ❌ | ❌ | ❌ | ✅ | ✅ |
Was this documentation helpful?