WordPress Restricted Site Access (SAR) - How To - Disable the Ability to Change the Password


How To Disable the Ability to Change the Password

Back to the user guides

Note: this feature was introduced in version 1.6.5.

The WordPress Restricted Site Access plugin allows to prevent users from changing their passwords. This feature is enabled specifically for each user. 

To find it, navigate to Admin Dashboard → Users → All Users.

Navigation to the list of site users - Content Dripping WordPress Plugin
Navigation to the list of site users

Choose the user which you want to prevent from changing the password, hover on his account and click Edit.

Editing the user - Tiered Membership
Editing the user

Find the section CM Site Access Restriction and check the option Disable ability to change the password. Then click the button Update User to save the changes.

Disabling ability to chage the password - Content Control WordPress
Disabling ability to chage the password

Result

If the user has access to his user profile settings, after turning on the option he will not be able to see the option Set New Password.

Result on the back-end - Page Restriction WordPress
Result on the back-end

If the user tries to use the option Lost your password?, he will see the message that he is not allowed to do this.

Result on the front-end - WordPress Restrict Content
Result on the front-end

TIP

The error message can be customized in plugin settings. To find it, navigate to Admin Dashboard → CM Site Access Restriction Pro → Settings â†’ Labels tab. You can edit the option in the field disable_password_error_message. Don't forget to save the changes after editing it.

Changing the front-end label - Content Gate
Changing the front-end label

More information about the WordPress Restricted Site Access plugin

Other WordPress products can be found at CreativeMinds WordPress Store

Let us know how we can Improve this Product Documentation Page

To open a Support Ticket visit our support center
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.