WordPress: Roles, Capabilities, and Application Passwords
WordPress has shipped a complete user and permissions system since long before āauth as a serviceā was a category. If the site is built on WordPress, accounts are already solved, not a feature to add.
Out of the box, WordPress ships five roles: Subscriber, Contributor, Author, Editor, and Administrator. Each carries a set of capabilities (edit_posts, publish_posts, manage_options, and dozens more). Registration, login, and password reset screens already exist at /wp-login.php.
When the defaults donāt match a clientās team, custom roles and capabilities take a few lines:
add_role('reviewer', 'Reviewer', [
'read' => true,
'edit_posts' => true,
'publish_posts' => false,
]);
if (current_user_can('publish_posts')) {
// show the publish button
}
For headless or API-driven use (a mobile app, a decoupled frontend calling the WordPress REST API), Application Passwords let a user generate a scoped credential without exposing their real login password:
curl -u "admin:xxxx xxxx xxxx xxxx xxxx xxxx" \
https://example.com/wp-json/wp/v2/posts
When to reach for this
Any WordPress project. Reimplementing authentication next to WordPress core, instead of extending its role system, is wasted effort and a security liability.
When itās the wrong fit
A headless setup that wants token-based auth (JWT, OAuth) instead of Application Passwords. That flow is not part of WordPress core, so it needs a dedicated plugin, such as the JWT Authentication plugin.
Under the hood: WordPress capabilities are plain strings checked with
current_user_can(), stored as serialized PHP data against each role in the database. There is no formal permissions engine, which is why adding a custom capability is so easy: a string in an array, not a schema migration.