# Social media roles & permissions explained

> Owner controls billing, connected accounts & who else has access. Admin can manage most day-to-day settings but not ownership itself. Member can draft, schedule & publish within the accounts the workspace already has connected.

Updated: 2026-09-25.

## Why roles exist at all

Without roles, every person with access to a shared workspace has identical power: the ability to change billing, disconnect an account, remove another person, or post anything. That's rarely what a team actually wants, & roles exist to make the actual boundaries explicit instead of relying on everyone agreeing informally not to touch certain settings.

## The typical three-role shape

- **Owner**: full control, including billing, transferring ownership, & closing the workspace entirely
- **Admin**: can manage most day-to-day settings, social account connections, invites, but can't change roles or transfer ownership
- **Member**: can draft, schedule & publish using the accounts already connected, without access to billing or account-level settings

This shape covers the common need: one person ultimately accountable for the workspace, a smaller group trusted with operational control, & a wider group focused purely on the actual posting work.

## What each role should reasonably do

- Give **owner** to whoever is ultimately accountable for the workspace existing, usually the person who set it up or whoever's name is on the contract
- Give **admin** to whoever needs to connect new accounts, manage invites, or handle day-to-day settings without needing the owner involved every time
- Give **member** to anyone whose job is producing & scheduling content, without a reason to touch billing or account connections

Defaulting everyone to admin because it's easier than deciding roles individually usually just recreates the no-roles problem with extra steps.

## What roles don't replace

Roles control what a person is technically permitted to do. They don't replace an actual review step for what gets posted, since a member with full posting permission can still draft something off-brand or factually wrong. Permission & judgment are separate problems, & a role system solving one doesn't automatically solve the other.

DunSocial's draft-then-review flow exists specifically for the judgment side, regardless of which role actually wrote the post.

## DunSocial's specific role structure

DunSocial uses exactly this three-role model: owner, admin & member. Owner alone can manage billing, transfer ownership, or close the workspace. Admin can manage social account connections & invites. Member can create content with the workspace's connected accounts without reaching billing or account-level settings.

Every one of these checks runs the same way regardless of whether the request comes from the web app, the CLI, or MCP, so permissions don't quietly differ by which surface someone's using.

## Getting this right early

Assigning roles thoughtfully when a workspace is small, rather than defaulting everyone to the same level of access, avoids an awkward conversation later about downgrading someone's permissions once the team has grown & the informal trust that worked at three people stops scaling cleanly to ten.

Changing a role in DunSocial is a quick settings change either way, but starting deliberately avoids that conversation ever needing to happen.

## Related guides

- [How to set up a social media team in a shared workspace](https://www.dunsocial.com/hub/social-media-for-teams-and-agencies/how-to-set-up-a-social-media-team-in-a-shared-workspace.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)
- [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 happens when a team member leaves a social media workspace?](https://www.dunsocial.com/hub/social-media-for-teams-and-agencies/what-happens-when-a-team-member-leaves-a-social-media-workspace.md)

## About this document

This is the Markdown representation of https://www.dunsocial.com/hub/social-media-for-teams-and-agencies/social-media-roles-and-permissions-explained. 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