# What happens when a team member leaves a social media workspace?

> Removing someone from a workspace should immediately cut off their access without touching the connected accounts, drafts, or history they worked on. What needs deciding separately is whether any drafts they left in progress still need finishing.

Updated: 2026-09-25.

## What should happen immediately

Removing a departing team member's access should be immediate & complete: no more ability to log in, draft, schedule, or view the workspace. This shouldn't require disconnecting & reconnecting the actual social accounts, or disrupting anything already scheduled, since the workspace itself & everything in it belongs to the organisation, not to any one member.

## What shouldn't need touching

- Connected social accounts, which stay connected regardless of who leaves
- Already-scheduled posts, which should continue publishing on schedule
- Post history & past drafts, which stay part of the workspace's record

A departure that forces reconnecting accounts or losing scheduled content is a sign the access model was built around individuals rather than the shared workspace, which creates real risk every time someone leaves.

## What genuinely needs a decision

- Any draft the departing person left unfinished: does someone else pick it up, or does it get discarded
- Any personal access token or automation they set up under their own name, which likely needs reassigning to someone still on the team
- Whether they held the owner role, which needs resolving before removal, not after

Unfinished drafts are usually the easiest to handle: reviewing what's in progress before removing access lets someone triage rather than discovering an abandoned draft weeks later.

## The one case that needs handling before removal

If the departing person is the workspace owner, ownership needs transferring to someone else first. Removing an owner without transferring first either isn't allowed or leaves the workspace in an awkward state, since a workspace needs exactly one owner at all times.

Handling this transfer as part of the offboarding conversation, not as an afterthought once someone's already gone, avoids the scramble. DunSocial requires exactly this: an owner transfers to another active member before that owner's own access can be removed.

## How DunSocial handles this

Removing a member from a DunSocial workspace revokes their access immediately without touching the connected accounts, the calendar, or anything already scheduled, since all of it belongs to the workspace rather than to that person's own login.

Any personal access token they created gets revoked as part of removing their account access, so an old integration doesn't keep running under a departed person's credentials.

## A reasonable offboarding checklist

Reviewing in-progress drafts, confirming ownership isn't tied to the departing person, & revoking their access on their actual last day rather than some vague point afterward covers the real risk here. Treating this as a routine step, not an afterthought handled only when someone remembers, keeps a workspace's access list accurate as a team changes over time.

DunSocial's role & access settings make each of these a quick, deliberate action rather than something buried in a settings page nobody checks.

## Related guides

- [Social media roles & permissions explained](https://www.dunsocial.com/hub/social-media-for-teams-and-agencies/social-media-roles-and-permissions-explained.md)
- [How to transfer ownership of a social media workspace](https://www.dunsocial.com/hub/social-media-for-teams-and-agencies/how-to-transfer-ownership-of-a-social-media-workspace.md)
- [What is a personal access token & how does it secure API access?](https://www.dunsocial.com/hub/social-media-automation-for-developers/what-is-a-personal-access-token-and-how-does-it-secure-api-access.md)
- [How to onboard a new team member to social media management](https://www.dunsocial.com/hub/social-media-for-teams-and-agencies/how-to-onboard-a-new-team-member-to-social-media-management.md)

## About this document

This is the Markdown representation of https://www.dunsocial.com/hub/social-media-for-teams-and-agencies/what-happens-when-a-team-member-leaves-a-social-media-workspace. The HTML version of the same page is at the same URL. You can also request Markdown from any page by sending `Accept: text/markdown`.

Machine-readable summary of the whole site: https://www.dunsocial.com/llms.txt

## Company

- Product: DunSocial, https://www.dunsocial.com
- Legal entity: THISUX PRIVATE LIMITED, Chennai, Tamil Nadu, India
- Support: support@dunsocial.com
- Open the app: https://app.dunsocial.com/login