Projects

A project is one brand, initiative, or product you publish for. Each project has its own:

• Channels — the social accounts you publish from (TikTok, LinkedIn, Instagram, …)
• Sources — where the raw content comes from (CDN, Notion, Supabase, RSS, …)
• Brand voice — tone, audience, signature phrases, visual style
• Logo + brand assets — used on posts and in the dashboard
• Content — the items, drafts, and scheduled posts belong to this project

Switching projects in the sidebar changes everything you see in the dashboard to that brand. Sources tab, Channels tab, Content tab, autopilot — all filter to the active project.

Workspace vs. Project — what's the difference?

Workspace	Project
Your account (the company / person who signed up)	A brand or initiative inside that account
Billing & members live here	Content, channels, voice live here
You usually have one workspace	You usually have many projects
Example: "Acme Inc."	Example: "Acme Main Site", "Acme Newsletter", "Acme DE"

In the sidebar, the top switcher (orange/amber) is your workspace; the bottom switcher (violet/fuchsia) is the active project inside it.

Don't worry if you only see one workspace — that's the default. Most users never need to create a second one. Projects are where the action is.

Create your first project

When you sign up, the onboarding flow walks you through this as the first step. If you skipped it, or want to add another:

1. Click the project switcher at the top of the sidebar (the violet square + project name)
2. Click Create Project at the bottom of the dropdown
3. Type a name — e.g. Acme Main, My Personal Brand, Pinpulse
4. Done. The project is created and selected. Logo + voice come next.

Project Settings — name, logo, voice

Open the project switcher → click Project Settings.

Three tabs:

General

• Rename the project at any time
• Slug is permanent (used internally — it's set when you create the project)
• Brand hub slug override — only relevant if your project name on the brand hub differs from your project slug here (e.g. project slug frederike-falke vs. hub slug frederikefalke)
• Write & Autopilot toggle — see below
• Delete project — destructive, asks for confirmation. Will fail with a friendly error if the project still has channels or content attached; remove or move those first.

Write & Autopilot

Controls whether the Create and Autopilot tabs appear in the dashboard for this project.

• On (default) — you can write posts manually in the Create tab and generate scheduled content via Autopilot.
• Off — those two tabs are hidden. Use this when a project only publishes content ingested from external sources (Supabase, Notion, your CDN, etc.) and your team doesn't need an internal writing surface for that brand.

Turning it off doesn't delete any existing posts or topics — they stay in the database, just hidden from the sidebar until you flip the toggle back on. You can change this at any time and it takes effect immediately for the active project. The same option appears in onboarding (pre-selected by default — deselect if your workflow is external-sources only).

Logo

• Upload a PNG, JPG, GIF, or WebP (up to 10 MB)
• Preview, replace, or remove
• The logo replaces the violet initial square in the sidebar — easier to spot at a glance when you manage multiple brands
• Lives at the project level, so every member working on this project sees the same logo
• Coming soon: opt-in watermark on generated visuals

Voice

See the Brand Voice page for the full picture.

Switching projects

Click the project switcher in the sidebar → pick another project. The page reloads so every list re-fetches scoped to the new project's content.

If you have a topic, draft, or post that should belong to a different project than the one you're in, switch projects first, then create it. Sources, channels, and content created in project A stay in project A.

Inviting team members to one project (only)

Per-project member roles (e.g. "this freelance designer can only see TIRIDA") are on the roadmap, not yet self-serve. If you need this for a real engagement, reach out: hi@amplicast.io — we'll set it up in the meantime.

Today, members invited to your workspace can see all projects in that workspace.

How projects relate to billing

Billing is at the workspace level, not per project. Your subscription covers everything across all projects in the workspace.

The post-quota counter (e.g. "100 posts per month") aggregates across projects, so publishing 40 from TIRIDA + 60 from Nxtconnect uses the full 100 — there's no per-project quota.

FAQ

Can a channel post for two projects? No. A channel belongs to exactly one project. If you genuinely need the same TikTok account to post for two different projects, today the simplest path is two TikTok app connections (one per project). We can model "shared accounts" cleanly when there's enough demand — let us know.

What happens to a project's content if I delete the project? Today deletion is blocked while content/channels exist — you'll need to move or delete them first. We're considering an "archive" option that hides a project without losing its content; tell us if that's what you'd want.

Can I rename the slug? No. The slug is permanent because it's used as an identifier internally and in the brand hub mapping. Display name is free to change.

What if I'm managing 20 brands? That works. You'll likely want a clear naming convention so the project switcher stays scannable (tirida-en, tirida-de, etc.). Logos help too. If you're running an agency at scale and want a "favorites" or grouping feature in the switcher, ping us at hi@amplicast.io.