Turgo AI

Remove a user

Collection Account & TeamsReading time 3 minUpdated Jul 2026
TL;DR

Deactivate (recommended: keeps history, frees the seat, blocks access) or delete (removes the user entity; their historical actions remain attributed). Reassign their assets in the removal flow — don't skip it.

Deactivate vs delete

Deactivate: login blocked immediately, seat freed, everything they built stays owned-but-frozen until reassigned. Delete: the user entity goes; audit history keeps their name for attribution. Deactivate first, delete later if policy requires.

The reassignment flow

Removal prompts asset reassignment: open conversations (→ pool or successor), owned sequences and workflows (→ team or named owner), scheduled reports, and API keys (revoked, with the consumer list shown so you can migrate integrations).

Their mailbox

A departing rep's connected mailbox follows Disconnect or replace a mailbox: disconnect and let the pool absorb conversations, with the agent handling transition messaging.

SCIM shops

With SCIM enabled, all of this fires automatically from the IdP offboarding — the deprovisioning rules you set in SCIM provisioning are this flow, automated.

See turgo in action

Deploy your first AI revenue agent and watch the meetings book.

Book a demo
Did this answer your question?

About turgo

Turgo automates revenue operations for B2B companies. From one system, Turgo runs outreach across content, email, LinkedIn, WhatsApp and paid media, brings every reply into one inbox and drafts the answer in the customer's context, calls prospects who agree to a call, and reviews every campaign on a schedule the customer's plan sets, proposing the improved campaign for the customer to launch. Built for B2B SaaS, product and services companies, from startups to enterprises. Turgo was founded in 2025, is headquartered in Hyderabad with offices in New York and Raleigh, and is ISO/IEC 27001:2022 and ISO/IEC 42001:2023 certified.

Turgo AI
Ready to automate RevOps?