Skip to main content

WordPress Roles & Capabilities

Overview

Roles are how users are grouped within WordPress.

Each role is allowed to perform a set of tasks called Capabilities. It is those capabilities that define what a user with a specific role can or can’t do.

Capabilities are in effect a permissions system.

WordPress by default has six roles: Super Admin, Administrator, Editor, Author, Contributor and Subscriber. Although roles are not hierarchical, the default roles do set up what appears to be a hierarchical system.

The Super Admin role only applies to WordPress Multisite installations.

The default set of capabilities assigned to each WordPress role is listed in detail in the Capability vs Role table on WordPress.org. It can help you better understand which capabilities are assigned to roles in your installation.

It is important to note that while these roles each come with a pre-defined set of capabilities, they can very easily be changed by using a plugin such as Members or by developers directly within their own code/plugin.

WordPress only allows one of the default roles to be assigned to any particular user.

However WordPress does technically support the idea of more than one role per user. Developers of plugins can create their own roles. They can assign certain capabilities to those roles that, within their plugin, control what users with those roles can and can’t do.

An example of this is the WooCommerce.

  • Customer: Assigned to new customers when they create an account on your website. This role is basically equivalent to that of a normal WordPress subscriber, but customers can also edit their own account information and view past or current orders.
  • Shop Manager: This allows the user to run the operations side of your WooCommerce store without the ability to edit back-end functionality like files and code. A manager has the same permissions as a customer, plus they’re also granted the ability to manage all settings within WooCommerce, create/edit products, and access all WooCommerce reports.

Another example is the bbPress plugin.

The default bbPress roles and associated capabilities created by the bbPress plugin are:

  • Keymaster – Can create, edit and delete other users’ forums, topics and replies. Can manage Tags, and moderate a forum with the moderation tools. Has access to global forum settings, tools, and importer.
  • Moderator – Can create and edit forums. Can create, edit and delete other users’ topics and replies. Can manage Tags, and moderate a forum with the moderation tools.
  • Participant – Can create and edit their own topics and replies.
  • Spectator – Can only read topics and replies.
  • Blocked – All capabilities are explicitly blocked.

ActiveMember360 and WordPress Roles

ActiveMember360 does not create any additional WordPress roles. Nor does it change the capabilities assigned to any roles.

When a WordPress user is created by ActiveMember360 they are given the WordPress role as specified in WordPress, Settings, General, New User Default Role.

Control Login To WordPress Based Upon Roles

ActiveMember360 does not provide features to control a login to the WordPress site using Roles.

Control Access To Content Based Upon Roles

When using ActiveMember360 Conditionals you can control access to content on any page or post based upon the WordPress user role.

Conditionals and WordPress Page Builders

Conditionals can be used with:

  • Beaver Builder - Modules, Columns & Rows
  • Beaver Themer - Conditional Logic & Layouts
  • Elementor - Widgets, Sections & Popups
  • Oxygen Builder - Elements
  • WordPress Block Editor - Blocks
  • WordPress Classic Editor
  • WordPress Menus
  • WordPress Widgets
  • …and many other theme and content builders that support shortcodes

Setting Roles Based Upon ActiveCampaign Tags

ActiveMember360 includes a Role To Tags module to allow WordPress roles to be added or removed based upon the ActiveCampaign tags of the logged in user.