Advanced Access Manager

+760k downloads
+60k websites
+2.5k dev hours

Advanced Access Manager was created in 2011. After releasing version 1.0, the web community allowed my first plugin (AAM) to speak for itself as it has become one of the most popular access manager plugins on WordPress with over 700k downloads. Such a positive response suggested that we had created a powerful tool that would allow businesses and individuals to further control and customize the access of their websites. In 2016 we have released AAM version 3 with the main focus on design, simplicity, power and usability.

Today, AAM is one of the most popular access control plugins. It is an easy-to-use, but at the same time, very powerful tool that gives you a flexible control over your either single WordPress site or Multisite Network. With AAM, you are allowed to configure access to different parts of your website for any role, individual user or visitor.

Check the frequently asked questions belong to get a better understanding on AAM subject.

Action Panel

Download AAM

  • AAM Plus Package $30 USD
  • AAM Redirect $20 USD
  • AAM Content Teaser $10 USD
  • AAM Role Hierarchy $15 USD
  • AAM Role Filter $5 USD
  • AAM Complete Pack $70 USD

Questions? Contact Us

Advanced Access Manager main and the only objective is to control access to your posts, pages, custom post types, categories, comments, media files, metaboxes, dashboard widgets, frontend widgets and admin menu. In order to perform this task successfully, AAM also has an easy-to-use user interface to manage your roles, users and capabilities.
Many times customers get confused with our concept of extensions. So please be aware that we do not offer any "pro version" and prefer to spit additional functionality in separate extensions that serve very specific goals. For example AAM Plus Package is dedicated to extend access control for posts and pages; while AAM Role Filter is more for user and role management purpose. This way we can keep the cost of our products low and customers buy only what they need rather than everything as one big "pro package".
Yes. We are human-beings and truly believe in better world. If you are a nonprofit organization or your budget is very limited, send us a message with what your organization is doing and what extension you are looking for. Please notice! If you are too lazy to introduce yourself and your objectives, we simply will ignore your email.
By purchasing an AAM extension customer obtains only the right to have an extended piece of functionality. This does not include any kind of customer support unless it is related to extension bugs. All AAM extensions have been tested and verified by thousands of users. Based on 2015 statistics, there are at least around 20 thousands of extended AAM installations around the globe; which leave almost no room for any kind of bugs.
Yes. In case you are not satisfied with the purchased AAM extension, you have full rights to ask for refund within 30 days. Please submit refund form above with explanation and we will issue the full refund within 2 business days.
Through last couple years, we’ve been “blest” to deal with quite few users that blamed AAM for screwing their websites; but if they read the AAM description carefully, they would know that AAM is deeply integrated with core and is based on WordPress capabilities. That is why it is very important to understand how roles and capabilities work in WordPress. To summarize, AAM is not designed for inexperienced user but rather for advanced WordPress administration or as handful tool for custom WordPress development. No matter how experienced you are, make sure that you always have a recent database backup in case of any unexpected issues.
//Get AAM_Core_Subject. This object allows you to work with access control
//for current logged-in user or visitor
$user = AAM::getUser();

//Example 1. Get Post with ID 10 and check if current user has access to read it
//on the frontend side of the website. If true then access denied to read this post.
$user->getObject('post', 10)->has('frontend.read');

//Example 2. Get Admin Menu object and check if user has access to Media menu.
//If true then access denied to this menu
$user->getObject('menu')->has('upload.php');