Pular para o conteúdo
NovoVeja como
Melhoria

Edit member roles and per-workspace permissions

Team admins can now change an existing member's role and fine-tune their access workspace by workspace.

Managing team access used to require removing a member and re-inviting them whenever their role or workspace access needed to change. That friction is gone. Team admins can now update roles and permissions inline, with changes applying immediately and no disruption to the member's active session.

More control over your team

You no longer need to remove and re-invite someone to change their access. Role and workspace changes take effect immediately — no re-authentication required on the member's side.

How to use it

  1. Open Settings → Team → Members.
  2. Click a member's role chip to change it inline — no re-invite needed.
  3. Click their workspace badge to grant or revoke access workspace by workspace.
  4. Connector management rights can be controlled per member, too.

Role menus also got smarter: they stay fully visible near the bottom of the screen instead of getting clipped by the viewport edge.

What you can control

The update gives admins precise, per-member control across three dimensions:

  • Role — change a member's organization-level role directly from the members list without a remove-and-reinvite cycle.
  • Workspace access — grant or revoke access to individual workspaces without affecting the member's role or their access to other workspaces. Useful when a team member's scope changes, a new workspace is spun up for a new market or client, or access needs to be narrowed for operational reasons.
  • Connector rights — control whether a member can manage email connectors, independently of their broader role.

Why it matters

For small sales teams running multiple outbound campaigns across different segments or clients, workspace-level access control is essential. The right person should be able to see and edit the campaigns they own without touching the ones they don't. Being able to adjust that on the fly — without the friction of a re-invite cycle — means your team structure can evolve as fast as your outreach strategy does.

It also matters for security hygiene. When someone's scope changes — a new hire gets narrower access, a contractor wraps up a project, a team reorganizes — you can reflect that immediately rather than leaving stale permissions in place while you work through a re-invite queue.

Changes take effect immediately and don't interrupt the member's session. There's no confirmation email on their end, no re-login required — the next page they load simply reflects their updated access. You stay in control without creating friction for your team.

Todas as novidades

Prospecção que continua quando você desconecta.Leads, emails, follow-ups e respostas, resolvidos.

Conecte caixas ilimitadas e deixe os agentes de IA encontrarem leads, escreverem cada email e fazerem follow-up. Ou envie seus próprios modelos no modo manual. A partir de $29/mês.

$1 por 3 dias · Cancele quando quiser · Sem contrato

Instalar com IA

Seu agente de código configura a CLI e as skills do FirstSales para você.

Prompt para 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.