We are closing the hyper-support for recently launched AAM 6 and pleased to announce that it was, for the most part, successful rollout. Yes, there were some hiccups and critical errors caused by incompatibility with other plugins, however, we solved them all and extremely grateful for everybody who provided feedback.
It is time to look forward and we are launching the new phase in AAM evolution, which is new features development and here is the list of features that we are planning to release in the upcoming AAM 6.2.0
- Explicit control over website areas for content visibility. In AAM 6 we consolidated Posts & Terms access options and no longer have separation between frontend, backend and API levels. We also renamed bunch of access settings to be more relevant to what they actually do.
Two options that we completely misjudged are HIDDEN and HIDDEN TO OTHERS. It is also the most complicated option to implement as it took us at least 3 years to make it right. We've been asked by multiple persons to have a more granular way to manage areas where content should be hidden and visible. That is why, just for this access option, we are enhancing AAM UI with such a possibility.

Multisite tooling. For those who are still wondering if AAM is multisite compatible, we would like to say Yes. AAM, like any other plugin, is compatible and functioning perfectly fine on multisite setup. The only thing that is missing is the ability to navigate between sites more efficiently and/or sync access settings between them. That is why we are merging back the functionality that was once available in AAM 5 with Multisite extension. You should expect to find the following new features in AAM 6.2.0 core:
~ Ability to navigate between sites from the main network site (the same way it was done in AAM 5 and Multisite extension);
~ Ability to automatically sync roles across all sites;
~ Ability to automatically sync access settings (Backend Menu, Redirects, URI Access, etc.) across all sites;
~ New Access Policy resource SITE;
Ability to send support messages from the dashboard (for the Enterprise level customers only). The scale comes with its own challenges. While we still do not differentiate between free and paid customers, some require much faster and reliable response time. That is why for customers that have Enterprise License, we give the ability to connect with us in a more streamlined and easy way.
Export/Import all AAM settings. Yup, that feature is coming back, however, we are changing the way it is functioning. While in AAM 5 you could import/export AAM settings on the Tools->Import
and Tools->Export
pages, in AAM 6.2.0, this functionality will be available on the AAM Settings Area tab. Because we also changed the way access settings are stored, we are changing the format of exported settings.
Ability to generate access policy based on user's access settings. We are taking the access policy directly extremely seriously and believe that it already disrupts the WordPress access management industry. Many companies already using access policies as their primary way to manage access settings, now we are making it easier to actually create them.