Reference

Introduction

Thank you so much for your interest in the most powerful and flexible WordPress access control plugin Advanced Access Manager (aka AAM).

This documentation contains the complete list of all features that AAM 5.0 or higher has. Some of the sections have reference to articles that explain related feature in-depth.

Please do not hesitate to contact me if you are not able to find answers to your questions.

Getting Started #back to top

WordPress CMS (content management system) got very popular over past few years because of its simplicity and flexibility. However it is not as simple and intuitive when it comes to manage access to a WordPress website. From this documentation you will learn from the inside-out all you need to know about WordPress core and how to manage access to it with AAM plugin.

Some sections may have highlighted paragraphs with three different colors based on the user’s experience level and as well as warning message.

Green color - absolute beginner or end-user without any programming knowledge
Yellow color - experienced website administrator who familiar with FTP, databases etc.
Dark blue - expert with PHP programming knowledge
Highlighted Red - important notification (warning)

How to Install AAM #back to top

AAM is the free WordPress plugin that hosts in the official WordPress plugin repository. To install it, simply go to your website WordPress backend area and navigate to the Plugins->Add New. Here you can search for Advanced Access Manager and install it on your website.

AAM Installation
Please Note! AAM is WordPress plugin, so you need to have already WordPress CMS installed in order to use it.

Upon AAM activation, no additional steps are required. You will be able to find the new AAM menu item on the main admin menu sidebar.

UI Overview #back to top

AAM is quite complex plugin with over 100 different features however most of the development time was spent on creation of the intuitive and easy-to-use UI to maximize webmaster efficiency.

AAM UI Overview

The UI interface is divided into 6 distinct areas that are designed to either display important information or to give you the ability to do some specific set of actions. There are also several pieces of functionality that go beyond the AAM page and are integrated with WordPress UI like Access Manager Metabox or Access Link.

Area #1. Current Subject #back to top

The Subject, in AAM context, is a general definition for role, individual user, visitor or default access to everybody. Other words the Subject is who you manage access to.

AAM Current Subject

Each time you change subject on the Users/Roles Manager area, the current subject banner is adjusted accordingly. This gives you the visual confirmation for who are you managing access to.

The current subject can be highlighted with two colors. The red color means that you are managing access to the highest allowed user level or to the default access for everybody. That is why be careful as you can accidentally restrict access to your user. Additionally the entire AAM page will have the light red background.

Notice! Access to AAM UI is customizable and you can grand access to certain features for anybody who is registered on your website. For example you can give ability for your Editors to manage access to Posts & Pages. For more information about this feature please check How to manage access to AAM page for other users article.

The blue color indicates that you are managing access for role or user that has lower user level than you do.

Area #2. Main Panel #back to top

The Main Panel is were all the magic happens. Here you have all the necessary set of tool to manage access to your website frontend and backend.

AAM Main Panel

The panel is divided on two sub-areas

  • - list of tabs (features) like Backend Menu, Capabilities, Login Redirect etc.;
  • - control area is the place were you actually manage access settings;

Each tab contains collection of tools grouped by logical meaning and they are described in-depth further in this documentation.

Area #3. Settings Area #back to top

AAM is highly customizable plugin. There are multiple ways you can alter its behavior and the easier one is through the Settings Area.

AAM Settings Area

The layout here is similar to the Main Panel where all settings are grouped based on the logical meaning. Here you can find the most widely used settings.

Please Note! It is strongly recommended at least to glance through the list of all available settings because they can help you to significantly improve your website performance. WordPress, inherently, was not designed for advanced customization. That is why some AAM features may reduce your website performance and if you do not use resource consuming features, you can disable them.

Area #4. Extensions Area #back to top

As it was mentioned already, AAM is highly customizable plugin. You can extend AAM functionality with extensions.

AAM Extensions Area

AAM comes with set of premium extensions that you can purchase in our online store as well as several free extensions that can be downloaded from the Extensions area.

You can create your own custom extension. For more information check the Developers page.

Area #5. Users/Roles Manager #back to top

Users/Roles Manager is the place where you can manage list of roles, users, visitors as well as default access for everybody. It has a lot of neat features and they all are described in-depth in the Users/Roles Manager section.

AAM User Role Manager

Area #6. Notification Manager #back to top

The Notification Manager was added in the AAM 4.0 version to visually show important notifications that require website administrator's attention.

AAM Notification Manager
Note! Mostly these notifications are warning and do not stop AAM to function properly. However it is strongly recommended to address and resolve a notification.

Access Manager Metabox #back to top

By default every post, page or custom post type will have additional metabox added to the edit screen that allows to manage access to it for any user, role, visitor or default access to everybody for both frontend and backend.

AAM Access Manager Metabox
The metabox can be turned off with Render Access Manager Metabox option.

Secure Login Widget #back to top

AAM comes with its own secure login widget & shortcode that you can use to drop on your frontend page. It has couple cool features that can significantly improve your website security.

AAM Secure Login Widget
The secure login functionality can be turned off with Secure Login. For more information about secure login widget check How does AAM Secure Login works article.

Core Concepts #back to top

To be truly expert in the WordPress access management, you would have to be aware about all the conceptual and functional pieces that WordPress core has. As it was mentioned in the UI Overview section, AAM is just the useful tool that you can help to customize your website access however it is your responsibility to be familiar with how WordPress core works so you can do administrative tasks more efficiently.

Please Note! You do not have to be an expert in programming to understand basic concept below however by knowing them, I promise, you can save many-many hours of work and hundreds or even thousands of dollars.

Basics #back to top

WordPress is based on the hybrid of Role-Based Access Control (RBAC) and Access Control List (ACL) models. It is designed to give the ability for a website owner to control what other users can or cannot do based on the assigned role. On other hand, it also has the limited ability to customize access for a specific user (this part is explained in-depth in the What is a WordPress user article).

It is very critical to understand the WordPress Roles & Capabilities as it is the core concept for access management.

With that knowledge you are capable of creating complex membership platforms or simply manage access to restricted parts of your websites with little to no effort.

Roles #back to top

By default, the WordPress website has Administrator, Editor, Author, Contributor and Subscriber roles. The crucial difference between them is in the amount of assigned capabilities that sometimes is mistakenly referred to “user or role levels”.

The User Levels concept was introduced to the WordPress 1.5, replaced with Roles and Capabilities in 2.0 and finally announced as deprecated in 3.0. In the current WordPress implementation, the user levels are represented as the list of capabilities level_0 to level_10 and they do not have any impact on the user permissions.

To learn more in-depth about the roles please refer to the What is a WordPress role article.

Users #back to top

WordPress comes with straight-forward user management functionality. You can create unlimited number of users and delegate different responsibilities based on the assigned role.

List of all users can be found in the backend on the All Users page, however it is accessible only for users that have aam_manager_users capability or are administrators.

The default WordPress functionality does not support the idea of user status. Every registered user is considered as active however with AAM you have the ability to deactivate users without actually deleting them or even setup temporary user account. For more information about this please refer to How to manage WordPress users article.

Visitors #back to top

Anybody who is not authenticated (logged in) is a visitor. Typically they have access only to the frontend side of a website and have limited abilities to interact with frontend features.

WordPress core has almost no tools to manage what visitors can or cannot do on the frontend side however AAM has a lot of features that you can utilize to manage access not only to the frontend content and widget but also access to the entire website.

For more detailed information about the WordPress visitors, please check Who is a WordPress visitor article.

Capabilities #back to top

Capability is the core concept in the WordPress access management as it literally defines what authenticated user is authorize to do. However it is important to emphasize that it is heavily utilized for the backend side of a website.

The Roles & Capabilities article is probably the best reference to all predefined core capabilities that come with default WordPress installation.

To learn more about WordPress capabilities and how you can use AAM to manage them, please refer to the What is a WordPress capability article.

Frontend #back to top

Frontend is the publicly facing part of the WordPress website. Typically it is rendered by the active theme and consists of pages, posts, categories widgets and menus.

WordPress core does not have any abilities to manage access to it however AAM has a lot of neat feature that can be used. You can manage access almost to every part of your frontend.

For more information please refer to the What is the WordPress frontend article.

Backend #back to top

Backend is usually restricted part of the WordPress website. This is the place were only authenticated users have access to.

Typically the list of tasks that authenticated user can perform in the backend is defined by the assigned capabilities. That is why it is very important to understand the concept of capabilities.

For more information about backend and how AAM manages access to it please check What is the WordPress backend article.

There are many different ways to programmatically connect to a WordPress website however two became dominant in past 10 years. One API type is based on XML-RPC standard and another is RESTful.

With AAM you can manage access to individual API endpoints for any role, individual user or visitors as well as complete disable them.

WordPress Hooks #back to top

WordPress hooks is the subject of interest to developers rather than none technical users however it is beneficial to understand the concept because majority of customization is based on hooks.

Hooks are programmatic actions and filters that can be used by developers to “hook into” some core WordPress functionality. For example AAM hooks into the functionality that retrieves the list of posts from the database and filter out all posts that are hidden for currently authenticated user or visitor.

The User Activity extension uses hooks to listen to different user actions and stores all related information and shows you the detailed report when requested.

There are few core WordPress functions that developers can use to register new hooks. Internally they are executed the same way with the only difference in returned result. The add_action function does not return any result while add_filter action has to return the input value either unmodified or modified, otherwise it will break the chain of functions that may hook to the same event. It is also important to pay attention to the priority attribute as lower priorities are executed first.

A lot of access management tasks cannot be accomplished just with roles and capabilities that is why you may noticed that developers refer to different hook that can be utilized to accomplish desired objectives. Please do not hesitate to contact me if you are not sure how to accomplish some of the tasks and I'll be more than happy to help you out.

Posts, Pages & CPTs #back to top

WordPress functionality is built around the concept of posts. Every page, post or custom post type (CPT) is a post and the only thing that differentiate them is the post type.

All posts are stored in the database table wp_posts and the post_type colum defines the post type.

AAM plugin has many access options that you can use to manage very granular access to any post.

For more information about the concept of posts please refer to the What is a WordPress post article.

Taxonomies #back to top

WordPress posts can be grouped together with taxonomies and there are two different types: hierarchical and tags.

AAM Taxonomies

For example post category is a hierarchical taxonomy and you can create a complex tree of categories with sub-categories. However post tags is a linear list of tags that can be assigned to a post.

AAM works only with hierarchical taxonomies and greatly enhance your ability to manage access to large amount of posts that are grouped. For more information about the taxonomy check What is a WordPress taxonomy article.

Inheritance Mechanism #back to top

AAM has the most sophisticated access settings inheritance mechanism that is available online for the WordPress CMS. It takes in consideration all WordPress core relationships between website resources. Under resource I mean any post, taxonomy, user, role, menu, metabox etc.

With Role Hierarchy extension you can even create a hierarchical tree of WordPress roles where all child roles inherit settings from parent.

It is very important to understand how it works because with this knowledge you have endless possibilities. Within minutes you can create a complex membership portal that typically would cost you thousands of dollar to implement from scratch.

For more information about inheritance mechanism please refer to How does AAM inherits access settings article.

Users/Roles Filter #back to top

AAM utilizes the deprecated User Levels concept to enhance WordPress backend security.

For more information about this feature please check WordPress Users and Roles Filter article.

AAM Caching #back to top

AAM has internal caching that stores access settings to posts and terms because this is the most time and resource consuming procedures due to access inheritance mechanism.

It is important to emphasize that cache is stored per each individual user separately and is automatically cleared if user's role is changed. It is also automatically cleared if any changes detected for hierarchical terms like categories or posts, pages or custom post types.

For more information about AAM cache, please refer to the How does AAM cache works article.

AAM Settings #back to top

In this section you'll find all AAM settings & tools that you can utilize to change the default AAM behavior.

Note! Some features may reduce your website performance. Read carefully description for each option and apply them based on your needs.

Get Started Tab #back to top

The Get Started tab is more like an informational part of the AAM UI. Typically it is oriented for just a beginners and contains some useful information regarding where to start with AAM. You may disable this tab is you just want to focus on managing access to your website resources.

Edit/Delete Capabilities #back to top

By default, the ability to edit or delete any capability is disabled to prevent from unforced mistakes. So many inexperienced WordPress users lost control over their website because of that so I've made the decision to disable it unless it is explicitely enabled.

When option is enabled, two additional icons are available for each capability: "Edit" and "Delete".

AAM Manage Capabilities
To learn more about the ability to manage capabilities with AAM please refer to How to manage WordPress capabilities article.

Backend Access Control #back to top

Toggle access control over the backend area.

Keep this option disabled if you are not managing access to your website backend side. This may increase your website performance.

By disabling the Backend Access Control feature, AAM UI will adjust accordingly and following features will be removed:

Frontend Access Control #back to top

Toggle access control over the frontend area.

Keep this option disabled if you are not managing access to your website frontend side. This may increase your website performance.

By disabling the Frontend Access Control feature, AAM UI will adjust accordingly and following features will be removed:

API Access Control #back to top

Toggle AAM control over the RESTful or RPC-XML APIs.

Keep this option disabled if you are not managing access to your website API side. This may increase your website performance.

By disabling the Frontend Access Control feature, AAM UI will adjust accordingly and following features will be removed:

Render Access Manager Metabox #back to top

Access Manager Metabox, by default, is added to every edit screen for posts, pages, media attachments, CPTs, categories or custom taxonomies. You can disable this metabox if there is no need to manage access to your website content or you simply want to hide it.

Please note! The Access Manager metabox is not rendered for users that do have access to AAM page or do not have ability to manage AAM Posts & Terms feature. It is also not rendered when all Frontend Access Control, Backend Access Control and API Access Control options are disabled.

Secure Login #back to top

AAM has its own secure login widget and shortcode that you can drop on your website frontend. It is the AJAX-based login functionality that does everything what default WordPress login has and very well integrated with AAM core. Additionally it takes in consideration security settings that AAM has that can significantly improve your website security.

For more information about secure login feature please check How does AAM Secure Login works article.

XML-RPC WordPress API #back to top

XML-RPC API is one of the major features that WordPress core offers. It allows other applications to programmatically communicate to your website and do things like fetch list of posts, edit any or create new. The complete list of available actions you can find in the official WordPress codex.

With AAM you have ability to completely disable the XML-RPC API and any attempts by other applications to work with your website through this channel will be denied.

Note! If you are looking to disable only certain components of the XML-RPC API, you better consider to restrict them with API Routes feature.

There are quire few talks online about either this feature should be enabled or disabled so my recommendation is going to following:

Recommendation. If you do not understand what is XML-RPC and/or you absolutely sure that not a single active plugin on your website uses it, then keep XML-RPC API disabled. No need to have another backdoor to your website.

RESTful WordPress API #back to top

RESTful API is probably the most popular way to programmatically connect your website with other applications or even another WordPress website. It is widely used these days by many plugins. Even AAM has few RESTful endpoints declared for things like JWT authentication or payment webhooks.

With AAM you have ability to completely disable the RESTful API and any attempts by other applications to work with your website through this channel will be denied.

Note! If you are looking to disable only certain RESTful endpoints, you may consider to restrict them with API Routes feature.
Recommendation. If you do not understand what is RESTful API and/or you absolutely sure that not a single active plugin on your website uses it, then keep RESTful API disabled. No need to have another backdoor to your website.

JWT Authentication #back to top

This features adds additional HTTP endpoint to the WordPress RESTful API where you can authenticate user with JWT token.

For more information about JWT authentication feature please check How to authenticate WordPress user with JWT token article.

Support AAM Extensions #back to top

Sometime there is a need to disable the ability to install or load AAM extensions. For example WordPress VIP environment is very strict about what can be installed and they require to disable any file system interaction that are triggered by any plugin. By disabling extension support, AAM will not load any installed extensions as well as Extensions Area will be removed from the area panel.

AAM Cron Job #back to top

AAM has internal job that utilized WordPress cron job functionality to check periodically if there are any new updates available for already installed extensions. If your WordPress website is on the intranet or behind restricted firewall, it makes sense to disable a cron job.

Note! AAM does not trigger a cron job if there are no extensions installed.

When AAM triggers a cron job there are only 3 pieces of information shared with aamplugin.com server: website domain, list of premium licenses and unique AAM ID that was assigned to your domain. This information is used only to track where premium licenses have been installed as typically all AAM licenses are valid for one live domain only.

To learn more about AAM information privacy please check our Privacy Policy page.

Multisite None-Member Restriction #back to top

WordPress multisite network does not have any options to manage access to sites per user base on the frontend. That is why any user or visitor can access all sites in the network. Enabling Multisite None-Member Restriction option allows AAM to block access to sites for users that are not members of the sites (not added as users of the site).

Please note! AAM will control only frontend access. To restrict user to access backend area for any site, simply do not add user to the site's user list.

Media Files Access Control #back to top

AAM is probably the only free plugin that gives the ability to manage physical access to all your media assets. By enabling Media Files Access Control option, all restricted to READ media assets will not be accessible to view or download.

Please Note! Additional steps are required to configure this feature. For more information please check How to manage access to the WordPress media library article

Check Post Visibility #back to top

Deprecated! This option has been deprecated and removed in the AAM 5.4 version. AAM functionality was highly optimized and can be used on large website without performance impacts.
Enabling Check Post Visibility feature may slow-down the website performance with large amount of posts, pages or media library.

WordPress core database and functionality is not normalized for granular acess management to its resources like posts, pages or categories. It would be much easier if all the Website content and relations between different content types were static however in reality this is not true. We consistently adding new posts and categories, changing how they are organized, creating new users and roles. AAM successfully takes in consideration these facts however it comes with the cost.

When Check Post Visibility option is enabled AAM applies settings inheritance mechanism for each fetched post or term and cache result per user base. When there is large amount of posts, AAM will do it in small portions.

It is recommended to keep this feature disabled if you are not planning to use Posts & Terms access option LIST or LIST TO OTHERS.

Manage Hidden Post Types #back to top

By default, AAM lets you manage access to post types that are public (check the public parameter's definition) however this might not satisfy all possible scenarios.

For example, the frontend menus are typically list of hidden post types nav_menu_item that are references to the actual posts, pages, categories or links. The mentioned post type is hidden (not public) that is why you need to explicitely enable the ability to manage them. Upon enabling, you should be able to see more post types available for access control on the Posts & Terms tab.

AAM Hidden Post Types

Page Categories #back to top

Note! Available with Plus Package extension only.

WordPress, by default does not provide the ability to group your pages in categories the same way as posts. This might be very useful if you are planning to manage access to multiple pages. Upon enabling this feature, you will be able to group pages into categories the same way as posts.

AAM Media Category

Media Categories #back to top

Note! Available with Plus Package extension only.

WordPress, by default does not provide the ability to group your media library in categories. This might be very useful if you are planning to manage access to the group of files. Upon enabling this feature, you will be able to group media assets into categories the same way as Posts.

AAM Media Category

Support Multiple Categories #back to top

Note! Available with Plus Package extension only.

It is quite common when you have to assign more than one category (any hierarchical taxonomy) to a post. In some instances you may have multiple hierarchical taxonomies registered for a post.

AAM by default takes in consideration only access settings from the first category and ignores others however by enabling Support Multiple Categories option, AAM will fetch access settings for all assigned hierarchical taxonomies and merge them as following:

  • - By default the denied access option has higher priority. For example if for Category A all posts are allowed to READ, however for Category B all posts are restricted to READ, then any post that has Category A and Category B will be not allowed to READ.
  • - If ConfigPress option access.merging.preference* is set to allow then with the same scenario as above, the post will be allowed to READ.
AAM Access Merging
Please Note! The LIST and LIST TO OTHERS options are the only exception to these rules due to a lot of constrains with the way WordPress posts are stored in the database. AAM will show a post if any of the assigned categories allow to LIST or LIST TO OTHERS.

* You should have Plus Package 3.5.1 or higher for this feature.

Inherit From Parent Post #back to top

Note! Available with Plus Package extension only.

Allow AAM to inherit access settings from a parent post (any hierarchical post type like pages) before trying to inherit settings from a parent category or default settings.

For more information about AAM post access inheritance mechanism please check How to manage access to the WordPress content article.

Login Timeout #back to top

The Login Timeout is the easiest and the most efficient way to slow down any brute-force attacks on your website. Typically when you send a login request to the WordPress core, it takes about 50 to 100 milliseconds to get response. By enabling Login Timeout option, the login request slows down to 1 second. So technically this means that it will slow down any attack x10 to x20 times and significantly reduce change for criminals to get access to your website.

Note! If you concern that slowing down login for 1 second will negatively impact user experience please answer yourself this question. Does it really so bad to wait 1 second for one-time action?
For more information about AAM Secure Login functionality please refer to the How does AAM Secure Login works article.

One Session Per User #back to top

The One Session Per User option ensures that the same user is logged in at one location only. So for example if John Dawn logged in the school library in the morning and forgot to logged out, he can simply login from his home computer or even mobile phone and this will destroy the active session that he opened in the school library. Very good feature if you wan to reassure that there is only on session per user active on your website.

For more information about AAM Secure Login functionality please refer to the How does AAM Secure Login works article.

Brute Force Lockout #back to top

By enabling the Brute Force Lockout option, AAM will count number of login attempts per IP address and if there are 20 failed consequent attempts to login, all further request will be automatically blocked for next 20 minutes.

For more information about AAM Secure Login functionality please refer to the How does AAM Secure Login works article.

Backend Menu #back to top

One of the most popular features that AAM offers is the ability to restrict access to the backend menu items. AAM not only filters out restricted menus and submenus but is also prevents direct access to them.

AAM Backend Menu
To learn more about admin menu and how AAM can help you manage access to it, please check How to manage WordPress backend menu article.

Admin Toolbar #back to top

With AAM v5.4 or higher you have the ability to filter out unnecessary items from the top admin toolbar.

AAM Admin Toolbar
Note! Admin Toolbar feature is not intended to restrict direct access to URLs and should be used only to remove unnecessary items from the top admin toolbar. Use Backend Menu tab to restrict direct access to backend pages or utilize the great power of roles and capabilities.
If you are looking to complete hide admin toolbar on the frontend for any roles or individual users, you can create a custom capability show_admin_bar and make sure that it is not checked for desired role or user.

Metaboxes & Widgets #back to top

Another useful feature that comes with basic AAM plugin is the ability to manage list of metaboxes and widgets on both frontend and backend.

Metaboxes and widgets are parts of the backend and frontend, designed to do very specific tasks. You can find metaboxes on edit post, page or custom post type pages. For example "Publish", "Categories", "Custom Fields" etc. are metaboxes.

Widgets typically are rendered either on the Home page of the admin Dashboard or on the sidebar of the website frontend.

The AAM v5.3.4 or higher also filters out restricted widgets from the Appearance->Widgets backend page.
AAM Metaboxes and Widgets
To learn more about metaboxes and widgets and how AAM manages them, please refer to the How to hide WordPress metaboxes and widgets article.

Capabilities #back to top

This is the most powerful and also very sensitive part of the entire website. Be careful because you can easily loose control over your website or restrict group of users from doing critical tasks without even noticing that.
AAM Capabilities

On this tab you have absolutely all necessary tools to manage list of capabilities for any role or even individual user.

To learn more about the concept of capability and how AAM manages them please check What is a WordPress capability article.

Additionally AAM introduces numerous custom capabilities that you can utilize to enhance your website functionality. All the available AAM custom capabilities are listed below.

aam_manager #back to top

By default only users with Administrator role have access to the AAM page however you can change this behavior by adding a custom aam_manager capability. Any user or role that has this capability assigned also will have access to the AAM page.

To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_admin_menu #back to top

Give ability for other users to manage Backend Menu access.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_admin_toolbar #back to top

Give ability for other users to manage Admin Toolbar access.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_metaboxes #back to top

Give ability for other users to manage Metaboxes & Widgets access.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_capabilities #back to top

Give ability for other users to manage Capabilities.

To give the ability for other user to manage capabilities is almost like giving the complete access to the website. You have to really trust your user in order to give access to this section.
Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_posts #back to top

Give ability for other users to manage Posts & Terms access. This capability used to check if user has the ability to work with Access Manager Metabox on a post edit screen.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_access_denied_redirect #back to top

Give ability for other users to manage Access Denied Redirect.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_login_redirect #back to top

Give ability for other users to manage Login Redirect feature.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_logout_redirect #back to top

Give ability for other users to manage Logout Redirect feature.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_404_redirect #back to top

Give ability for other users to manage 404 (Not Found) Redirect feature.

Keep in mind that 404 redirect can be managed only on the default level so your user also has to have the aam_manage_default capability.
Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_ip_check #back to top

Note! Available with IP Check extension only.

Give ability for other users to manage access to your website by visitor's IP address or referred host with IP Check feature.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_settings #back to top

Give ability for other users to manage AAM Settings feature.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_extensions #back to top

Give ability for other users to manage AAM Extensions feature.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_show_notifications #back to top

Give ability for other users to see the AAM console panel with notifications.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_default #back to top

Give ability for other users to manage Manage Default Access to all users.

This feature allows to manage access to everybody, including all administrators.
Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manage_visitors #back to top

Give ability for other users to manage Manage Visitors.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manager_roles #back to top

Give ability for other users to the Manage Roles feature however keep in mind that the list of roles will be filtered based on the current user level and user will be able to list only roles that have lower user level.

There are also several additional capabilities aam_create_roles, aam_edit_roles, aam_delete_roles that can be used to manage more granular access to what exactly user can do with the list of roles.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_manager_users #back to top

Give ability for other users to the Manage Roles feature however keep in mind that the list of roles will be filtered based on the current user level and user will be able to list only roles that have lower user level.

There are also several additional capabilities aam_create_roles, aam_edit_roles, aam_delete_roles that can be used to manage more granular access to what exactly user can do with the list of roles.

Your user or role also has to have aam_manager capability assigned. To learn more about access management to the AAM page itself, please refer to the How to manage access to AAM page for other users article.

aam_create_roles #back to top

Sorry... Still working on documenting this.

aam_edit_roles #back to top

Sorry... Still working on documenting this.

aam_delete_roles #back to top

Sorry... Still working on documenting this.

aam_toggle_users #back to top

Sorry... Still working on documenting this.

aam_switch_users #back to top

Sorry... Still working on documenting this.

aam_manage_configpress #back to top

Sorry... Still working on documenting this.

aam_manage_api_routes #back to top

Sorry... Still working on documenting this.

aam_display_license #back to top

Sorry... Still working on documenting this.

show_admin_notices #back to top

Sorry... Still working on documenting this.

manage_same_user_level #back to top

Sorry... Still working on documenting this.

show_screen_options #back to top

Sorry... Still working on documenting this.

show_help_tabs #back to top

Sorry... Still working on documenting this.

access_dashboard #back to top

Sorry... Still working on documenting this.

allow_ajax_calls #back to top

Sorry... Still working on documenting this.

show_admin_bar #back to top

Sorry... Still working on documenting this.

delete_comment #back to top

Sorry... Still working on documenting this.

approve_comment #back to top

Sorry... Still working on documenting this.

edit_comment #back to top

Sorry... Still working on documenting this.

moderate_comments #back to top

Sorry... Still working on documenting this.

spam_comment #back to top

Sorry... Still working on documenting this.

reply_comment #back to top

Sorry... Still working on documenting this.

trash_comment #back to top

Sorry... Still working on documenting this.

unapprove_comment #back to top

Sorry... Still working on documenting this.

untrash_comment #back to top

Sorry... Still working on documenting this.

unspam_comment #back to top

Sorry... Still working on documenting this.

Posts & Terms #back to top

AAM plugin has the most powerful and sophisticated set of tools to manage access to the website posts, pages, media, custom post types, categories and custom taxonomies. Flexible inheritance mechanism and multiple levels of default settings makes AAM the best content management plugin that is available for the WordPress CMS.

AAM Content Access Control

You can manage access to your content for any role, individual user or visitors for both frontend and backend.

To learn more in-depth about this please check How to manage access to the WordPress content article.

Below is listed all available access options that can be used to define more granular access to your website content.

Hide any post on the website frontend or backend. AAM will filter out selected post from all menus or lists however it can be accessed with direct URL. For example, you can hide the page "Sample Page" for all users with the Subscriber role but if user has direct URL to the page, he will be able to access it.

With Plus Package extension access control is also available for taxonomies or you can even setup default access to any registered post type (e.g. Posts, Pages, Media etc.).

LIST TO OTHERS #back to top

Note! Available with Plus Package extension only.

Similar to the LIST option however a post is hidden for everybody except the author (whoever is listed as an author of a post). It is also probably one of the most confusing options and requires additional explanation.

List to others technically means that you restrict to show a post to none-authors within the scope that you manage access to. For example, if on the Users/Roles Manager you selected Editor role, then LIST TO OTHERS means, that restricted post will be hidden from all users that have Editor role and are not the author of a post.

Keep in mind! It absolutely makes no sense to use LIST TO OTHERS option for an individual user because that particular user cannot be "others" as well as "others" can not be that user. That is why LIST TO OTHERS options is not displayed when you manage access to posts or terms for an individual user.

If you want to hide posts from all users except authors, then you should switch to manage default access settings. These settings are propagated to all users and role automatically unless overwritten.

Note! If LIST TO OTHERS and LIST options are both checked, then AAM disregards LIST TO OTHERS option.

Restrict access to read a post. If LIST option is not checked, then the post is still listed on the website frontend but direct access to it is restricted. Any attempt to access a post will be denied and user will be redirected based on the Access Denied Redirect rule.

Media library is the exception. To learn more about this topic check How to manage WordPress media access article.

READ BY OTHERS #back to top

Note! Available with Plus Package extension only.

Similar to the READ option however the post is restricted for reading and viewing for everybody except an author (whoever is assigned as author or a post). It is also one of the most confusing options and requires additional explanation.

Read by others technically means that you restrict to read a post to none-authors within the scope that you manage access to. For example, if on the Users/Roles Manager you selected Contributor role, then READ BY OTHERS means, that a post will be restricted to read by all users that have Contributor role and are not the author of a post.

Keep in mind! It absolutely makes no sense to use READ BY OTHERS option for an individual user because that particular user cannot be "others" as well as "others" can not be that user. That is why READ BY OTHERS options is not displayed when you manage access to posts or terms for an individual user.

If you want to restrict access to read posts by all users except authors, then you should switch to manage default access settings. These settings are propagated to all users and role automatically unless overwritten.

Note! If READ BY OTHERS and READ options are both checked, then AAM disregards READ BY OTHERS option and the author will not be able to read his own posts.

LIMIT #back to top

Limit access to a post by showing a custom teaser message. It is useful to use this option when you want to prompt user to do some action like login or renew subscription plan.

AAM Post Limit Option
The teaser message can be either plain text or valid HTML. For example with this custom HTML message the following can be shown instead of post's content.
<div class="text-center">
    <img src="https://aamplugin.com/imgs/access-key.svg" width="64" />
    <h2>Access Denied</h2>
    <p class="text-muted">Please contact our system administrator for more information</p>
</div>
AAM Custom Access Denied

READ COUNTER #back to top

Define how many times a post can be opened to read, view or download. This option is available only for authenticated users as there is no really secure way to identify visitors.

After user reaches defined threshold, access to a post will be denied and user will be redirected based on the Access Denied Redirect rule.

The read counter increments right after the threshold is set. The counter is stored in the wp_usermeta table as aam-post-[post-id]-access-counter meta key. There is no option to reset this counter from the AAM UI. The meta key has to be deleted manually when there is a need to reset the counter.

COMMENT #back to top

Restrict access to write comments on a post. For example you can restrict access for visitors to write comments on any post to reduce the amount of spam.

REDIRECT #back to top

Redirect user or visitor based on the specified redirect rule when any user or visitor is trying to access a post.

AAM Post Redirect

There are several possible redirect rules that can be choose:

  1. Redirect to existing page. Will redirect user to a different page.
  2. Redirect to the URL. Will redirect user to a specified URL.
  3. Trigger PHP callback function. Will trigger callable and valid PHP callback.
Note! If you just want to restrict access to a post, then use READ option instead.

PASSWORD PROTECTED #back to top

Available with WordPress 4.7.0 or higher.

Password protect a post. This is very similar to the password protected feature that WordPress core offers however AAM extends it and allows to setup a password for any category or all posts.

For example you can define a single password for all pages but overwrite it for one specific page.

It has been reported several times that some of the custom themes do not support password protected functionality. In this case you would have to work with your theme developer and if any questions, you may refer your developer to me via email support@aamplugin.com

ACCESS EXPIRATION #back to top

Define limited by time access to the post. For example you can allow visitors to access your posts in the Science category only for 1 month. After that the access will be automatically restricted.

AAM Post Access Expiration
For more information about this feature please refer to How to set expiration date on any WordPress content article.

MONETIZED ACCESS #back to top

Note! Available with E-Commerce extension only and can be enhanced with Plus Package extension.

Start selling access to your website content (any post, page, media asset, custom post type, category, custom taxonomy etc.). The option is based on the simple idea where authenticated user has access to "monetized" content only if he/she purchased related E-Product. Otherwise user will be automatically redirected to conduct a purchase or teaser message will be displayed to do so.

For more information about this feature, please refer to the How to monetize access to the WordPress content article.

Restrict access to edit a post or term. User will be able only to preview or delete a post or a term. Any attempts to edit it will redirect user based on the Access Denied Redirect rule.

Note! The basic AAM version allows to manage access to posts (any post, page, custom post type or media asset). With Plus Package extension you also can manage access to hierarchical terms.

EDIT BY OTHERS #back to top

Note! Available with Plus Package extension only.

Similar to the EDIT option however a post is restricted for editing for everybody except an author (whoever is assigned as author or a post). It is also one of the most confusing options and requires additional explanation.

Edit by others technically means that you restrict to edit a post to none-authors within the scope that you manage access to. For example, if on the Users/Roles Manager you selected Contributor role, then EDIT BY OTHERS means, that a post will be restricted to edit by all users that have Contributor role and are not the author of a post.

Keep in mind! It absolutely makes no sense to use EDIT BY OTHERS option for an individual user because that particular user cannot be "others" as well as "others" can not be that user. That is why EDIT BY OTHERS options is not displayed when you manage access to posts or terms for an individual user.

If you want to restrict access to edit posts by all users except authors, then you should switch to manage default access settings. These settings are propagated to all users and role automatically unless overwritten.

Note! If EDIT BY OTHERS and EDIT options are both checked, then AAM disregards EDIT BY OTHERS option and the author will not be able to edit his own posts.

DELETE #back to top

Restrict access to trash or permanently delete a post. Any attempts to trash or delete a post will be discarded.

DELETE BY OTHERS #back to top

Note! Available with Plus Package extension only.

Similar to the DELETE option however a post cannot be deleted by anybody except an author (whoever is assigned as author or a post). It is also one of the most confusing options and requires additional explanation.

Delete by others technically means that you restrict to delete a post by none-authors within the scope that you manage access to. For example, if on the Users/Roles Manager you selected Editor role, then DELETE BY OTHERS means, that a post cannot be deleted by all users that have Editor role and are not the author of a post.

Keep in mind! It absolutely makes no sense to use DELETE BY OTHERS option for an individual user because that particular user cannot be "others" as well as "others" can not be that user. That is why DELETE BY OTHERS options is not displayed when you manage access to posts or terms for an individual user.

If you want to restrict access to delete posts by all users except authors, then you should switch to manage default access settings. These settings are propagated to all users and role automatically unless overwritten.

Note! If DELETE BY OTHERS and DELETE options are both checked, then AAM disregards DELETE BY OTHERS option and the author will not be able to delete his own posts.

PUBLISH #back to top

Restrict access to publish an existing post if it haven't been published yet. Great option if you want to restrict access to publish content without reviewing it first. Any attempts to publish a post will result is saving the post with Pending Review status.

Note! If you are looking to disallow specific users or roles to publish newly created posts, then you would have to set default access to all posts for those specific users/roles. However for this purpose you have to have Plus Package extension.

PUBLISH BY OTHERS #back to top

Note! Available with Plus Package extension only.

Similar to the PUBLISH option however a post cannot be published by anybody except an author (whoever is assigned as author or a post). It is also one of the most confusing options and requires additional explanation.

Publish by others technically means that you restrict to publish a post by none-authors within the scope that you manage access to. For example, if on the Users/Roles Manager you selected Editor role, then PUBLISH BY OTHERS means, that a post cannot be published by all users that have Editor role and are not the author of a post.

Keep in mind! It absolutely makes no sense to use PUBLISH BY OTHERS option for an individual user because that particular user cannot be "others" as well as "others" can not be that user. That is why PUBLISH BY OTHERS options is not displayed when you manage access to posts or terms for an individual user.

If you want to restrict access to publish posts by all users except authors, then you should switch to manage default access settings. These settings are propagated to all users and role automatically unless overwritten.

Note! If PUBLISH BY OTHERS and PUBLISH options are both checked, then AAM disregards PUBLISH BY OTHERS option and the author will not be able to publish his own posts.

BROWSE #back to top

Note! Available with Plus Package extension only.

Restrict access to browse a category however it is still listed on the website frontend. When user clicks on the category's link, access to the category will be denied and user will be redirected based on the Access Denied Redirect rule.

For example you can restrict access to see list of products in the category "Products" for all visitors and redirect them to login page first.

ADD NEW #back to top

Note! Available with Plus Package extension only.

Restrict access to create new posts. This option is available only for default post type access level so technically you can either allow to create new posts or not. Any attempts to create a new post will be denied with WordPress core message "Sorry, you are not allowed to access this page."

There is no way to restrict access to create new posts for specific category simply because WordPress does not know what category you will choose after hit Create New button. To cover this scenario you can hide categories on the backend with LIST option.

Redirects #back to top

AAM plugin gives you several way to improve user experience with user redirects.

Currently AAM offers 4 different types of redirects and all, except 404 redirect, can be customized for any role, individual user or visitor.

Please note! All the features that are related to redirect are included in the free AAM version. There is no need to purchase any premium extensions.

Access Denied Redirect #back to top

Access Denied Redirect is very useful and granular feature that allows to define what AAM should be doing when access is denied for some restricted area.

AAM Access Denied Redirect
The UI functionality is self-explanatory however to eliminate any possible questions, please refer to the How to redirect WordPress user when access is denied article.

Login Redirect #back to top

By default, WordPress redirects user to the backend area after successful authentication. In a lot of cases this might not be the ideal user flow. With the Login Redirect feature you can redefine this behavior for any role or even individual user.

AAM Login Redirect

For example, you can redirect all users that have Subscriber role to any frontend page or URL, rather than to the backend, however all Editors, redirect to list of posts page on the backend.

The login redirect feature may not work if you are using third-party plugin or any custom functionality for the login process. We strongly encourage you to check our free AAM Secure Login feature.

Logout Redirect #back to top

Redefine logout redirect for any role or individual user. By default, logged out user is redirected to the default WordPress login screen which is not convenient at all. With this feature you can change to redirect user to website homepage or any other page and URL.

AAM Logout Redirect

404 Redirect #back to top

AAM allows you to define custom 404 redirect when page was not found on the website. The 404 redirect can be defined only on the default access level as it is less-likely you need the ability to define 404 redirect for specific user or role.

AAM 404 Redirect
For more information about this feature you can check How to redirect on WordPress 404 error article.

API Routes #back to top

This feature is available with AAM v5.3 or higher and allows to manage access to individual endpoints for XML-RPC and RESTful APIs. You literally can deny access to almost any endpoint for any role, user or anonymous requests.

For better RESTful API experience, you might want to consider JWT authentication that is already available in basic AAM version.
AAM API Routes
Please Note! I personally see a lot of potential in this feature, especially as a tool that can be used by other developers. So please do not hesitate to provide feedback or request additional features. I will keep adding them upon request.

URI Access #back to top

This feature is available with AAM v5.6 or higher and allows to manage access to any page on your website as long as it is rendered by WordPress core or third party application that loads WordPress core.

AAM URI Access
For more information about this feature check How to restrict access to any WordPress website URL article.

AAM Tools #back to top

AAM comes with predefined set of tools that you might find helpful during your access management setup. You can find them all on the Settings Area. They all are self-explanatory.

Export Settings #back to top

AAM has the ability to export all the access settings so you can import them to any other website. For example, it is very helpful when you want you have multiple website that should have the same list of roles and capabilities.

By default AAM exports only roles & capabilities, AAM settings and ConfigPress settings. You can customize this behavior with ConfigPress. For more information please check How to export and import AAM settings article.

Import Settings #back to top

Previously exported AAM settings can be imported to any WordPress website that have AAM installed.

To learn more about the import/export AAM feature please refer to the How to export and import AAM settings article.

Clear Cache #back to top

AAM comes with internal caching mechanism that is heavily used to cache posts and pages access settings. You can manually purge the cache.

AAM automatically clears the cache for specific user or all the users depending on the change. For example if you assign post to a new category, AAM will automatically clear the cache so a new set of access settings can be inherited.

Clear All Settings #back to top

To start fresh, you have the ability to clear all AAM settings however keep in mind that changes to the list of Roles and Capabilities are permanent and AAM does not reset them.

Users/Roles Manager #back to top

Users/Roles Manager is the sidebar panel on the AAM page that allows you easily navigate between roles, users, visitors or switch to manage default access to everybody.

Roles #back to top

WordPress allows you to have unlimited number of roles however it does not have ability to manage them. The Roles tab contains the list of all roles that are defined on your website.

AAM Manage Roles
To learn more about role management please refer to the How to manage WordPress roles article.

Users #back to top

With AAM Users tab you can see the list of all your users to manage access, block, define temporary user account or switch to any user to verify permissions.

AAM Manage Users
To learn more about user management, please check How to manage WordPress users article.

Visitors #back to top

AAM has the ability to manage access to the website visitors (users that are not authenticated).

AAM Manage Visitors
It is important to understand who is considered as visitor, so please refere to the What is a WordPress visitor article to learn more about it.

Default Access #back to top

One of the most powerful aspects in the AAM functionality is the ability to define default access for everybody to any website resource. So technically everybody (including Administrator role and your admin user) inherits default access settings unless overwritten.

AAM Manage Default Access
Please check How does AAM inherit settings article to learn more about AAM inheritance mechanism.

Shortcodes #back to top

AAM comes with set of helpful shortcodes that you can use to drop on within your post's, page's or custom post type's content.

Content Filter #back to top

Manage access to certain parts of a page/post content with [aam] shortcode. You can find more information about this shortcode in the How to filter WordPress post content article.

List of available attributes:

  • show - Comma-separated list of role IDs, user IDs or IP addresses to show content for;
  • hide - Comma-separated list of role IDs, user IDs or IP addresses to hide content from;
  • limit - Comma-separated list of role IDs, user IDs or IP addresses to limit content for;
  • message - Message to show if "limit" is defined attribute is defined;
  • callback - Callback function that return content;

Login #back to top

The [aam context="login"] shortcode is used to drop login form on your website page. To find more information about this shortcode please refer to the How does AAM secure login works article.

List of available attributes:

  • id - Unique login form ID. Default: random unique string;
  • user-title - Greeting message. Default: Howdy, %username%;
  • redirect - Redirect to page after successful login. Default: value in the __GET "redirect_to";
  • callback - Custom PHP callback function that returns login form. Default: none;

Extensions #back to top

AAM is very flexible WordPress plugin that can be easily extended based on the business custom need. It already comes with several free and premium extensions that you can find on the Extensions Area.

How to install #back to top

Please note! AAM extensions are not typical WordPress plugins and should not be treated as such. All AAM extension are installed in special directory that is outside of the default WordPress plugin directory.

There are two possible ways of installing AAM extension:

  • - From the Extensions Area. If you purchased a premium extension, then you can insert the license here and AAM will automatically download and install extension for you. For free extensions, you can simply click on Download button right next to the extension name.
  • - Manual installation. For example if you are behind the company firewall or your website has some troubles sending remote request to our server, you can download any extension and follow the manual installation instruction from the How to install AAM extension manually article.

Plus Package #back to top

AAM Plus Package is a premium extension that can be purchase from the online store.

Plus Package extends the default AAM Posts & Terms feature and allows you to manage access to post categories, custom hierarchical terms or set default access to all post types and even define default access to all posts, pages or custom post types. It also allows you to define more granular access to comments as well as gives you ability to group pages and media into categories.

You literally have no limit on defining how your content can be accessed by roles, individual users or visitors.
For more information about Plus Package extension, please refer to the AAM Plus Package page.

IP Check #back to top

AAM IP Check is a premium extension that can be purchase from the online store.

Manage access to your website based on visitor's IP address or referred host. Very useful extension if you looking to restrict access to your website for range of IPs or references from unwanted websites.

For more information about IP Check extension, please refer to the AAM IP Check page.

Role Hierarchy #back to top

AAM Role Hierarchy is a premium extension that can be purchase from the online store.

WordPress has linear role structure, so technically this means that a role cannot have a parent role. This limitation is eliminated with AAM Role Hierarchy extension.

For example, if you want to setup a website where Editors have the ability to manage posts however Regional Editors can manage posts only in regional category, while National Editor in national category, then you can simply define a generic Editor role where Regional Editor and National Editor inherit all access settings from parent Editor. From here you can customize only want is needed for a specific sub-role.

For more information about Role Hierarchy extension, please refer to the AAM Role Hierarchy page.

E-Commerce #back to top

AAM E-Commerce is a premium extension that can be purchase from the online store.

Start monetizing access to your website content with AAM E-Commerce. This extension gives you the ability to sell access to your webiste content with online merchants like Stripe and Braintree (PayPal company).

For more information about E-Commerce extension, please refer to the AAM E-Commerce page.

Multisite #back to top

AAM Multisite is a free extension.

The AAM Multisite extension allows you to manage access to all your sites from one centralized Network Panel. It has few convenient ways to jump between sites as well as sync access settings across all sites.

For more information about Multisite extension, please refer to the AAM and WordPress Multisite support article.

User Activities #back to top

AAM User Activities is a free extension.

User Activities extension tracks basic activities that users perform on your website. It is also very flexible extension and with some additional configuration you can literally track anything as long as there is a way to hook into a process with WordPress core hooks.

For more information about User Activities extension, please refer to the How to track any WordPres user activity article.

Social Login #back to top

AAM Social Login is a free extension however current it is still an alpha version.

Allow your visitors to login to your website with social networks like Facebook, Twitter, LinkedIn or Google. This extension adds few icons under the WordPress login form that allows visitor to choose the way to login to your website.

For more information about Social Login extension, please refer to the How does AAM Social Login works article.

Complete Package #back to top

AAM Complete Package is a bundle of extension that can be purchase from the online store.

Get the complete list of all premium extensions in one bundle. All future premium extensions will be included in the bundle for no additional cost.

For more information about Complete Package, please refer to the AAM Complete Package page.

Development Package #back to top

AAM Development Package is a subscription plan for complete bundle of premium AAM extensions that can be purchase from the online store.

All the premium AAM extension are valid for one live domain only however this the Development Package you can install complete list of AAM extensions on unlimited number of websites as long as you keep subscription active.

For more information about Development Package, please refer to the AAM Development Package page.

Useful Tools #back to top

For your convenience, there are sever tools that you can use below that help to work with AAM free and premium extensions.

  • - If you have issues downloading AAM extension for your website, you can do it manually with Download Extension tool;
  • - To transfer your existing license to a different domain, please find all necessary information in the Transfer License section;
  • - To generate a PDF version of the invoice, please use the Generate Invoice tool;
  • - If you want to request a refund, please submit a Refund Form below;

Download Extensions #back to top

Download
If you did not receive the email with license key, contact us immediately.

Select one of the available options to download
For more information about the manual installation process read How to install AAM extension manually

Transfer License #back to top

To transfer your license to a different domain, you have to deactivate it for already used one. To do so, please enter your license number below and you will be redirected to a page where you can manage your license.
Go To Manager My License

Generate Invoice #back to top

Request Refund #back to top

You can ask for refund within 30 days from the time of purchase. Please provide Transaction ID or License Key so we can find and refund your payment.

If you are requesting refund because you feel like AAM does not work, please consider to contact me first. 8 out of 10 times I was able to help within 24 hours.

Troubleshooting #back to top

There is no such a thing as “perfect plugin”. No matter how simple or complex functionality is, somewhere and for somebody it will not work as expected. A lot of times it has nothing to do with the plugin itself but rather misunderstanding of the features it offers or it is impacted by other plugin, or unusual website setup. That is why I firmly believe that quality of the plugin is not defined by how it was built, but how it is supported.

So please do not hesitate to contact me as soon as you start experiencing troubles, however consider to check How to troubleshoot AAM article before contacting me.

APPENDIX A. List of Article #back to top

Below you'll find the list of all articles that explain a lot of AAM features in depth.

Core WordPress Concepts: Core AAM Concepts: How to...?: