Create a Custom WordPress Role and Set Capabilities with Members
Create a staff role in Members, set its capabilities, test allowed and excluded actions, and preserve the role before major changes.

To give a staff member access to specific WordPress tasks without changing permissions for everyone, create a custom role in Members, select the capabilities that role needs, and assign it to a test account before using it for staff. For example, you can build a role for comment moderation and limited post work, then check that the account can moderate a comment but cannot publish a post. The important final check is the account itself: Members allows users to have multiple roles, which can make a role-only test misleading.
Start with capabilities, not a rank
A WordPress role is a set of capabilities, or permissions to perform particular tasks. Roles are not inherently hierarchical: a custom role does not need to sit “between” Editor and Administrator. Describe the work the person should do, then choose capabilities for that work.
After Members is installed and activated, open Members → Roles. That is the role-management screen used in the WordPress training lesson on Members. You can add a role there or use an existing role as a starting point.
Create a role without changing everyone else’s
For this example, call the proposed role Comment and Post Desk. If an existing role is close to what you need, clone it and edit the copy. Members supports both creating and cloning roles. Cloning is particularly useful when your starting point is a default WordPress role: changes to a default role made through Members are saved as permanent changes and must be reverted through the plugin. A copy lets you work on the staff role instead of changing the default role for its other users.
Alternatively, add a new role if no existing role is a sensible starting point. Before selecting capabilities, write a short task list for this example: moderate comments and edit posts, but do not publish or delete posts. If you cloned a role, inspect its existing selections too. A clone is a starting point, not proof that its permissions match your task list.
Grant the task, exclude the rest
In the role editor, grant Moderate Comments and select the post capabilities needed for the intended editing work. The WordPress lesson demonstrates granting Moderate Comments alongside post capabilities such as reading, editing, publishing and deleting. Here, publishing and deleting are not part of the proposed job, so do not grant them. Members also lets you explicitly deny capabilities you want unavailable to a role.
An unselected capability is not available to that role. That distinction matters: it does not establish what an account with other roles can do. Select only what the job calls for, review any capabilities carried over from a cloned role, and save the role. The first check is visible in Members → Roles: your new role should appear with the capabilities you intended to grant or deny.
Treat this as a consequential site change, not just a tidier dashboard. The Members plugin listing says the plugin makes direct changes to roles and capabilities in the database. If you have a staging site, it is a sensible place to prepare and check a substantial role change before applying it to the live site.
Assign it to a test user and check both sides
Assign Comment and Post Desk to a test user. Before drawing conclusions, inspect that account’s other assigned roles; Members permits more than one role per user. For the clearest check of this custom role, use a test account without another role that could grant the actions you are trying to exclude.
Sign in as that account and try the planned work. Can it reach the relevant dashboard feature and moderate a test comment? Can it perform the post-editing task you included? Then try an excluded action, such as publishing a test post. Record both the allowed result and the excluded result. Seeing the right menu is less useful than checking whether the account can actually complete the task.
If an intended action fails, revisit the role’s capability selections. If an excluded action succeeds, check the saved selections and the account’s other roles before treating the custom role as restrictive. The target outcome is specific: the test account performs the work you assigned to this role, cannot perform the excluded action, and has no overlooked additional role obscuring that result.
Preserve and revisit the role
Before a substantial revision, export the roles you need to preserve. Members can export selected roles from the roles table, or export all roles and Members settings to a JSON file. When importing roles, use the preview to inspect conflicts and choose whether to import, skip, overwrite or rename each role. Check the resulting role and repeat the account-level test; an export file alone does not verify the permissions now in use.
If you changed a default role rather than a copy, Members also provides an option at Members → Settings → Miscellaneous to reset the five default WordPress roles to their original capabilities. That is a broad reset, not a substitute for reviewing and testing the particular staff role you meant to maintain.
