---
title: "Understanding roles in your Buffer organization"
description: "Roles let you decide what each person in your Buffer organization can do, from managing billing and team members to drafting posts or viewing analytics. Every person has one role, and you choose which channels they can use it on. This article is for organization Admins who invite and manage teammates, and for anyone who wants to understand the access they've been given."
canonical_url: "https://support.buffer.com/articles/understanding-roles-in-your-buffer-organization-7hfOl6J4fz"
md_url: "https://support.buffer.com/articles/understanding-roles-in-your-buffer-organization-7hfOl6J4fz.md"
---
# Understanding roles in your Buffer organization

Roles let you decide what each person in your Buffer organization can do, from managing billing and team members to drafting posts or viewing analytics. Every person has one role, and you choose which channels they can use it on. This article is for organization Admins who invite and manage teammates, and for anyone who wants to understand the access they've been given.


:::info
**Note:** Roles is currently rolling out to Team plan organizations. If you don't see a **Role** dropdown when you invite or edit a team member, your organization hasn't been moved to Roles yet. See [Adding users and setting up permissions](https://support.buffer.com/en-us/articles/adding-users-and-setting-up-permissions-ixjiLpe2fd) for how access works in your organization today.

:::

## How roles work

Buffer has four roles: Admin, Creator, Collaborator, and Viewer. Each person in your organization has one of them.

A person's role and their channel access are set separately. The role decides what someone can do. Channel access decides which channels they can do it on. For example, a Creator with access to 3 of your 10 channels has full posting access on those 3 channels and no access to the other 7. Admins are the exception: they have access to every channel automatically. Everyone else starts with no channels until you choose them.

Each role has a default set of abilities, and that set is the most the person can do. Admins can turn specific abilities off for Creators and Collaborators (see "Customizing a Creator's or Collaborator's permissions" below), but they can't turn on anything the role doesn't include. If someone needs to do more, change their role.

The organization owner is an Admin. There is one owner per organization, and the owner is never locked if your organization moves off the Team plan.


:::info
**Note:** Team management is available in the web version of Buffer. Sign in to Buffer on a computer to invite people, change roles, or customize permissions.

:::

## What every role can do

Every role can:

* View a limited version of the Team Members page. People without the Admin role see themselves and the Admins of the organization, with each person's role, two-factor status, and channels. Admins see everyone.
* View posts, comments, and analytics on the channels they're assigned to.
* Create and manage their own Saved Views and Channel Groups.


 ![Invite Team Member screen.png](https://support.buffer.com/api/attachments.redirect?id=0e880e0c-d56e-4273-bf43-10ece39d569a " =852x768")


## The four roles

When you choose a role in the **Role** dropdown, you'll see a short description under each one. Admin is "Full control of the team and channels." Creator is "Can publish, comment and connect channels." Collaborator is "Can view, draft and add notes. Can't publish." Viewer is "View-only access to all assigned channels, plus can add notes."

### Admin

Best for: people who run the organization day to day.

Admins can do everything in the organization, and no one can customize their permissions. Admins can:

* Manage billing and the plan.
* Invite and remove team members, assign roles, and decide which channels each person can use.
* Manage organization settings, transfer ownership, and turn Beta features on or off.
* Connect, reconnect, and remove any channel.
* Publish, schedule, approve, edit, and delete posts on every channel.
* Manage media, ideas, feeds, templates, tags, saved replies, and hashtag groups.

Choose Admin access carefully, since Admins have full control over your organization.


:::info
**Note:** API keys are managed by the organization owner, not by every Admin. See "Who can create an API key?" in the FAQ below.

:::

### Creator

Best for: teammates or agency clients who publish and manage their own channels without running the organization.

On the channels they're assigned, Creators can:

* Publish and schedule posts directly, and approve or reject other people's posts.
* Create and edit their own posts and drafts, edit other people's posts, and delete posts.
* Reply to, react to, and dismiss comments and mentions.
* Edit channel settings and posting schedules.
* Export data and build reports in Insights.

Across the organization, Creators can:

* Connect and reconnect channels. A channel a Creator connects is assigned to them by default, and they can remove channels they connected. Only Admins can remove any channel.
* Publish the Start Page.
* Manage media, ideas, feeds, templates, tags, saved replies, and hashtag groups.

Creators don't manage billing, team members, or organization settings, and they can't give other people access to channels. For any of these, ask an Admin.

### Collaborator

Best for: teammates who create content and need approval before anything is published.

On the channels they're assigned, Collaborators can:

* Create and edit their own draft posts, and delete their own posts.
* View the queue, comments, and analytics, and add notes to posts.
* Export data and build reports in Insights.

Across the organization, Collaborators can:

* Upload, edit, and delete media, and create, edit, and delete ideas.
* View and use feeds, templates, tags, saved replies, and hashtag groups.
* Import content as drafts.

Collaborators can't publish or schedule posts directly, approve posts, edit other people's posts, reply to comments, edit channel settings, or connect channels. Their drafts go to an Admin or Creator for approval. See [Managing and approving draft posts](https://support.buffer.com/en-us/articles/managing-and-approving-draft-posts-57li7M8tDA) for how approval works.

### Viewer

Best for: clients and stakeholders who need visibility without editing access.

On the channels they're assigned, Viewers can:

* View the queue, posts, comments, and analytics.
* Add notes to posts, and edit or delete their own notes.

Across the organization, Viewers can view media, ideas, feeds, templates, tags, saved replies, and hashtag groups.

Viewers can't create posts, upload media, create ideas, or export data. A Viewer's access can't be customized, so if someone needs a bit more, change their role to Collaborator.

## Assigning a role

### Inviting someone with a role


1. Go to **_Settings_** → **_Team Members_** and click **_+ Invite Team Member_**. You can also click the **_+ New_** button in the top navigation bar and select **_Invite a Team Member_**.
2. Enter the person's email address and name.
3. Select a role from the **_Role_** dropdown.
4. Open the **_Channel Access_** dropdown and check the channels they can use. You can search for a channel or click **_Select all_**. Admins have access to every channel automatically.
5. If you chose Creator or Collaborator and want to turn specific abilities off, click **_Customize_** next to **_Custom Permissions_**. See the next sections for details.
6. Click **_Send Invite_**.


:::info
**Note:** Admins get access to every channel automatically. Creators, Collaborators and Viewers start with 0 channels, so choose the channels the person needs, or they won't see anything when they join.

For help with invitation emails, pending invitations, and removing people, see [Adding users and setting up permissions](https://support.buffer.com/en-us/articles/adding-users-and-setting-up-permissions-ixjiLpe2fd).

:::

 ![GIF of choosing a role, selecting channels, and clicking Send Invite.gif](https://support.buffer.com/api/attachments.redirect?id=2e7d232d-5ebe-40d3-8783-fd9b80e2b77d " =800x623")

### Changing someone's role


1. From your dashboard, click your profile avatar in the lower-left corner and select **_Settings_**.
2. Select **_Team Members_**. Click the three-dot menu on the person's row and select **_Edit permissions_**. The **_Edit Team Member_** dialog opens.
3. Select a different role from the **_Role_** dropdown.
4. When you choose a different role, the **_Save_** button changes to **_Review Changes_**. Click it. A **_Review Changes_** screen shows what's changing, such as "You are moving \[name\] from Admin to Creator".
5. Check the list of changes, then click the **_Change to \[role\]_** button to confirm. Click **_Back_** if you want to change something first.


 ![Review Changes in Customize Permissions](https://support.buffer.com/api/attachments.redirect?id=5044f496-3e52-4f9b-95af-4a14dd334d3f " =752x1298")

The **_Review Changes_** screen lists the organization-level abilities the person gains or loses, such as API and integrations, Beta features, organization settings, transferring ownership, managing billing, managing members, and deleting any note. It also shows how many of their other permissions stay the same.


:::info
**Notes:**

* Changing a role clears the person's customized permissions, so the new role's defaults apply.
* Changing a person's role or customizing their permissions takes you to the **_Review Changes_** screen. If you only change which channels they can access, click **_Save_** and you go straight back to the Team Members page, with no review step.

:::

## Customizing a Creator's or Collaborator's permissions

Customizing lets you turn off specific abilities for a Creator or Collaborator. For example, you could let a Creator draft posts on one client's channel without being able to publish there. Customizing only takes abilities away from a role's defaults. It never adds abilities, and it's available for Creators and Collaborators only. For Admins, the **_Custom Permissions_** row reads "Full Permissions", and it's greyed out for Viewers.

### Customizing permissions for a person


1. Open the **_Invite Team Member_** dialog or the **_Edit Team Member_** dialog, and select Creator or Collaborator as the role.
2. Choose the channels the person can use. Customize Permissions only shows channels they have access to.
3. Click **_Customize_** next to **_Custom Permissions_**. The **_Customize Permissions_** screen opens with two tabs: **_Channels_** and **_Organization Level Features_**.
4. On the **_Channels_** tab, select the channels you want to change from the list on the left. Their abilities appear on the right, grouped under Publish, Community, Insights, and Channel settings.
5. Switch off the abilities you want to remove. Your changes apply to the channels you've selected.
6. Open the **_Organization Level Features_** tab to switch off abilities that apply across your whole organization, such as managing the media library or ideas.
7. Click **_Apply_** to return to the invite or edit dialog.
8. Save your changes in that dialog: click **_Send Invite_** for an invitation. For an existing team member, click **_Review Changes_**. The screen reads "You are changing the permissions of \[name\]" and lists each ability that's changing, marked "Customized", along with how many other permissions stay the same. Click **_Save Changes_** to confirm, or **_Back_** to keep editing.


 ![GIF of customizing permissions](https://support.buffer.com/api/attachments.redirect?id=255afa6c-ba21-4e4f-bfd9-adc19d1c8b34 " =800x562")



:::tip
**Tip:** Looking for organization features while you're on the **_Channels_** tab? Click the **_Customize here_** link at the bottom to jump to the **_Organization Level Features_** tab.

:::


:::info
**Notes:**

* Customize Permissions doesn't save on its own. Nothing changes until you save in the invite or edit dialog. If you leave the screen without applying, you'll be asked whether to discard your changes.
* Abilities the role doesn't include appear switched off and greyed out. If you hover over one, it reads "For Creator or Admin only". Choose a higher role for that person instead.
* **_Reset Creator Defaults_** or **_Reset Collaborator Defaults_** returns the selected channels to the role's defaults.
* A switch you've turned off shows a dot and the word "Customized" next to it. The **_Organization Level Features_** tab also gets a dot when something on it is customized. Back in the invite or edit dialog, the **_Custom Permissions_** button shows how many abilities you've changed, such as "2 customized."

:::

### What you can customize

For Creators, on each channel you can turn off:

* Creating and editing their own posts and drafts.
* Editing other people's posts.
* Deleting their own posts and deleting other people's posts.
* Publishing and scheduling directly.
* Approving and rejecting posts.
* Replying to, reacting to, and dismissing comments and mentions. This is one switch. Mentions are available on the channels that support them.
* Exporting data and building reports.
* Editing channel settings.

For Creators, across the organization, you can turn off managing the media library, ideas, feeds, templates, tags, saved replies, and hashtag groups.

For Collaborators, on each channel you can turn off creating and editing their own draft posts, deleting their own posts, and exporting data and building reports. Across the organization, you can turn off managing the media library and ideas.

On the **_Organization Level Features_** tab, each ability is a single "Manage" switch, for example **_Manage tags_**. Turning one off doesn't hide the feature. It makes that feature view-only for the person, so they can still see it but can't create, edit, or delete anything.

Admins, the organization owner, and Viewers can't be customized. Their permissions always match their role.

## FAQ

### How do I give a client view-only access?

Invite them as a Viewer and choose the channels they can see. Viewers can see posts, comments, and analytics on those channels, but they can't create or edit anything.

### Can a Collaborator publish posts?

No. Collaborators create drafts, and an Admin or Creator approves them. If a teammate should publish without approval, give them the Creator role instead. You can then turn off publishing for specific channels if you need to.

### Can I give someone more access than their role includes?

No. A role's default abilities are the most someone can do, and customizing only turns abilities off. To give someone more access, change their role. If you'd like to see more flexibility, including custom roles, please share your idea at [suggestions.buffer.com](https://suggestions.buffer.com).

### Why can't the person I invited see any channels?

Every role except Admin starts with no channels. Go to **_Settings_** → **_Team Members_**, open **_Edit permissions_** for the person, and use the **_Channel Access_** dropdown to choose the channels they should see.

### What can a Creator do with a channel they connect?

Creators can connect and reconnect channels. A channel they connect is assigned to them by default, and they can remove channels they connected. Only Admins can remove other channels or give other people access to a channel.

If a Creator's role changes later, their abilities on that channel change with it. For example, if they become a Collaborator, they can no longer refresh or disconnect the channel, but they can still contribute drafts to it. If they're removed from the channel, they lose access to it, even if they were the one who connected it.

### What can people without the Admin role see on the Team Members page?

In **_Settings_** → **_Team Members_**, people without the Admin role see a read-only list of themselves and the Admins of the organization, with each person's role, two-factor status, and channels. If an Admin has customized someone's permissions, a "Customized" label shows under their role. The page doesn't list individual permissions, and people can't invite anyone or change anyone's role. Admins see everyone in the organization, along with pending invitations.

### Can a Creator see other clients' channels?

No, not unless they've been given access to those channels. A Creator only sees the channels they're assigned, so each client of an agency sees only their own.

### Who can create an API key?

API keys are tied to a user account rather than an organization, so the organization owner is the one who manages the keys for your organization. Anyone else can generate an API key from their own personal organization, and the API recognizes the other organizations they have access to.

### What happens to roles if our organization moves off the Team plan?

Everyone except the organization owner becomes view-only. Nobody is removed, and nothing is deleted. Buffer remembers each person's role, customized permissions, and channel access. If your organization upgrades back to the Team plan, everyone's access is restored automatically.

### What happened to my team's existing permissions?

When an organization moves to Roles, each person gets the role that matches their highest level of access today. Full posting access becomes Creator, Needs Approval becomes Collaborator, and View Only becomes Viewer. Having No Access on a channel doesn't change someone's role. They just don't get that channel. The owner becomes an Admin, and so does any Admin who had full access on every channel. Other Admins become Creators, which means they no longer manage billing, team members, or organization settings. If a Creator needs to manage billing, an Admin can change their role to Admin later.

On each channel, we apply customizations so people keep the access they had before. You can review and change any of it from **_Settings_** → **_Team Members_**.

## More resources

* [Adding users and setting up permissions](https://support.buffer.com/en-us/articles/adding-users-and-setting-up-permissions-ixjiLpe2fd)
* [Changing user permissions in your organization](https://support.buffer.com/en-us/articles/changing-user-permissions-in-your-organization-yWbzm5BIgH)
* [Getting started as a user in an organization](https://support.buffer.com/en-us/articles/getting-started-as-a-user-in-an-organization-euygyfky4N)
* [Managing and approving draft posts](https://support.buffer.com/en-us/articles/managing-and-approving-draft-posts-57li7M8tDA)


:::info
Need help with roles? Email [hello@buffer.com](mailto:hello@buffer.com) and our Advocacy team will be standing by to help.

:::
