Skip to content
NewSee how

How to Manage Organizations & Workspaces in FirstSales

Switch, create, and configure organizations and workspaces. When to split into a new workspace vs. a new org, and how member access is scoped.

Tutorials
Team & Workspace
min read
7 min
steps
7 · Beginner

  1. Organizations vs. workspaces

    An organization is your top-level account: it owns billing, members, and one or more workspaces. A workspace is a self-contained sending environment inside the org: its own mailboxes, campaigns, contacts, knowledge bases, and offerings. Use separate workspaces to keep clients, brands, or teams cleanly apart.

  2. Switch between them

    Use the switcher in the sidebar to move between organizations and workspaces. It shows your current org and workspace; pick another to change context. Everything you see (campaigns, contacts, settings) is scoped to the selected workspace.

    Switch between them

  3. Create a workspace

    From the switcher, choose Create workspace. The wizard asks for a name and basic profile. New workspace starts empty: connect mailboxes and build campaigns fresh. This is the right move for a new client or a distinct sending identity you don't want mixed with existing sends.

  4. Create an organization

    Need fully separate billing and membership? Create organization from the switcher. A new org has its own credit balance, plan, member list, and workspaces: nothing is shared with your other orgs. Most teams need only one org with several workspaces; reach for a second org only when billing or ownership must be separate.

  5. Configure organization settings

    In Settings, the organization section holds the org name, its ID (used by the API and CLI), industry, company size, and address. Keep these accurate: the org ID is what you pass to --org in the CLI, and the profile feeds AI context and billing records.

  6. Configure workspace settings

    Each workspace has its own profile plus a Default Contact Person: the fallback sender identity used when a campaign or contact doesn't specify one. Set this so drafts always have a sensible "from" persona. Workspace settings also gate which mailboxes and content that workspace can use.

  7. Scope people to workspaces

    Members and their permissions are workspace-scoped. When you invite someone, you choose which workspaces they can access and their role in them. This lets one org host multiple client workspaces where each contractor only sees the workspace they're assigned to.

Pro tips

  • One org, many workspaces: usually

    Separate workspaces (not separate orgs) is the right split for clients or brands: shared billing and members, isolated sending. Make a second org only when billing or ownership truly must be separate.

  • Set the Default Contact Person early

    It's the sender fallback for drafts. Configure it per workspace up front so no campaign ends up with a blank or wrong 'from' identity.

  • Keep the org ID handy for automation

    The org ID in Settings is exactly what the CLI/API want for --org. Grab it once and store it in your scripts' env instead of re-looking-it-up each time.

  • Isolate clients with workspaces

    A workspace per client keeps contacts, mailboxes, and campaigns from bleeding across accounts: and lets you scope each contractor to just their workspace.

Frequently asked questions

What's the difference between an organization and a workspace?

An organization owns billing, members, and workspaces. A workspace is an isolated sending environment (mailboxes, campaigns, contacts, KBs) inside the org. One org can hold many workspaces.

How do I switch workspaces?

Use the switcher in the sidebar to select a different organization or workspace. Everything in the app is scoped to whatever's selected.

When should I create a second organization?

Only when you need separate billing and membership. Orgs don't share credits, plans, or members. For separating clients or brands under one account, use multiple workspaces instead.

What is the Default Contact Person?

A per-workspace fallback sender identity used when a campaign or contact doesn't specify one. Set it so AI drafts always have a sensible 'from' persona.

Where do I find my organization ID?

In Settings, under the organization section. It's the value you pass as --org to the CLI and API.

Can a member be in some workspaces but not others?

Yes: access is workspace-scoped. On invite (or later via Edit workspace access) you choose which workspaces someone can reach and their role in each.

Team & Workspace

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗