Users, Roles and Permissions

Browse manual On this page × Wordpress Manual WordPress Fundamentals Toggle WordPress Fundamentals section What Is WordPress? WordPress.org vs WordPress.com What Can You Build with WordPress? How WordPress Works WordPress Core, Themes, Plugins and Content Essential WordPress Terminology How to Plan a WordPress Website Domains, Hosting, DNS and HTTPS Explained How to Choose WordPress Hosting…

3 min read

  • Article
  • 3 minutes read
  • Reviewed August 4, 2026

Learn how WordPress identifies users, controls access and assigns responsibility across a website.

The WordPress user system does more than provide usernames and passwords. It connects people to content, administration screens, editorial actions, application integrations and security decisions. Roles group common responsibilities, while capabilities determine whether a user can perform a particular action.

This section explains the complete system, from basic user profiles and default roles to custom permissions, editorial workflows, Multisite, privacy and troubleshooting.

Why User Architecture Matters

A website becomes harder to operate when every person receives administrator access or when permissions are assigned without a clear model.

Good user architecture helps a team:

  • Protect sensitive settings and data.
  • Separate publishing, reviewing and administration responsibilities.
  • Attribute content to the correct authors.
  • Reduce accidental changes.
  • Revoke access cleanly when responsibilities change.
  • Integrate external tools without sharing primary passwords.
  • Meet privacy and accountability requirements.

Permissions should be designed as part of the website architecture, not added only after a problem appears.

What This Section Covers

User Accounts and Profiles

Begin by understanding what a WordPress user represents, which profile data WordPress stores and how identities appear in the administration area and public content.

Start here: WordPress Users and User Profiles

Roles and Capabilities

Learn the difference between a role and a capability, compare the default WordPress roles and understand how WordPress evaluates permission checks.

These documents establish the vocabulary required before changing access rules or creating custom roles.

User Management and Registration

Explore how administrators add, update, remove and audit users. The registration guide explains the difference between creating accounts manually, enabling public registration and building a complete membership or onboarding workflow.

Authors and Editorial Responsibility

WordPress connects users with content authorship, ownership and revision history. This part explains how those relationships affect editing permissions, bylines, content transfer and team workflows.

Account and Integration Security

Learn how browser sessions, authentication cookies, password recovery, application passwords and two-factor authentication fit together.

Application Passwords are designed for programmatic access. They are not a replacement for the password used to sign in interactively.

Workflows and Custom Permission Models

Plan editorial responsibilities before changing capabilities. Then learn when custom roles are justified, how they should be registered and why capability checks should target actions rather than role names.

Multisite and Privacy

WordPress Multisite shares user identities across a network while assigning access per site. The final documents also cover personal data, export and erasure tools, account retention and permission troubleshooting.

Roles Are Not Individual Permission Checks

A role is a named collection of capabilities. A capability represents permission to perform an action, such as editing posts, managing options or updating plugins.

When code protects an action, it should normally check the required capability rather than asking whether the user has a specific role. Roles can be customized, and different roles may share the same capability.

Security Requires More Than a Strong Password

Account security combines several controls:

  • Unique user accounts.
  • Appropriate capabilities.
  • Strong passwords and protected recovery email.
  • HTTPS.
  • Two-factor authentication for privileged users.
  • Session review and revocation.
  • Application-specific credentials for integrations.
  • Timely removal of unused access.

No single control replaces the others.

A Practical Learning Path

Read the section in order when you are designing access for a new website. If you already manage WordPress users, begin with the page that matches your current task and follow its related links.

The section progresses from identity and default behavior toward custom implementation and operational maintenance.

Continue to WordPress Users and User Profiles

Start with the structure of a WordPress user account, the difference between identity and permissions, and the profile information associated with each account.

Next: WordPress Users and User Profiles