Skip to main content

Team Members

Amplicast supports multi-user workspaces with role-based access control. Invite colleagues to collaborate on content creation and publishing.

Roles

Four roles per workspace, in increasing order of permissions:

CapabilityViewerEditorAdminOwner
Read content, analytics, calendar, review queue & history
Create and edit posts, run AI transforms, schedule
Approve / reject items in the review queue
Approve / reject Autopilot drafts
Create / edit Autopilot topics + trigger generations
Manage personal Writing Style + Reference Library assets
Connect Bluesky and Reddit accounts
Create / edit content sources
Connect OAuth platform accounts (LinkedIn, Instagram, X, YouTube, TikTok, Facebook)
Rename, deactivate or delete connected accounts
Manage platform aliases
Change publish settings
Update workspace name & settings
Invite team members + remove non-owner members
Delete content sources
Change member roles
Delete the workspace
Manage billing — checkout, subscription, top-ups, billing portal

Per-project roles (for example "this contractor can only see the TIRIDA project") are not yet self-serve. They're on the roadmap. If you need this for a real engagement now, reach out: hi@amplicast.io.

Super-admin (separate concept)

There's also a super-admin role driven by the SUPER_ADMIN_EMAILS environment variable. It's an application-level role for the Amplicast operators (not per-workspace), and grants access to system-wide endpoints like cross-org cost dashboards. It does NOT appear in the role dropdown when you invite a workspace member.

Inviting team members

  1. Go to Team in the sidebar
  2. Click Invite Member
  3. Enter their email address
  4. Select their role (defaults to Editor)
  5. Click Send Invitation

The invited person receives an email with a link to join your workspace. If they don't have an Amplicast account yet, they'll be prompted to create one.

Managing members

From the Team tab you can:

  • Change roles — promote or demote team members (Owner only)
  • Remove members — revoke workspace access (Admin or Owner; you can also remove yourself unless you're the only Owner)
  • View pending invitations — see who hasn't accepted yet

Approval workflow

When team members create or generate content, it can flow through an approval process before publishing:

  1. Editor (or higher) creates a post, or Autopilot generates a draft
  2. Content appears in the Review Queue
  3. Any Editor (or higher) reviews, adds comments, and approves or rejects
  4. Approved content is published according to the schedule

:::info Coming soon Today any Editor can approve content. We're planning an opt-in toggle so workspaces can require Admin or Owner approval — useful for client-work setups where Editors draft but only senior team members publish. Tracked in publishing-alignment-roadmap §6. :::

What this guide does NOT cover yet

The features below exist on the roadmap but aren't self-serve yet — email hi@amplicast.io if you need them now:

  • Per-project member roles (e.g. "this freelance designer can only see one project")
  • Admin/Owner-gated approval (toggle described above)
  • SSO / SAML / enterprise auth