AIOS FAQ

The premium version of AIOS provides additional and more advanced security features. However, it's important to note that it relies on the free version as its foundation. So make sure you have the free AIOS plugin installed and activated before proceeding. 

Here's how to install AIOS Premium:

1. Head over to the AIOS webshop and purchase your preferred subscription.

2. You'll receive an email with a download link for the plugin. Alternatively, you can access the link by going to ‘My Account’ > ‘Licences / download’ on the AIOS site.

3. Log in to your WordPress admin dashboard.

4. Navigate to Plugins and then click on Add New Plugin.

5. Click on the Upload Plugin button at the top of the page.



6. Click on Choose file and select the downloaded AIOS Premium plugin zip file.

7. Click on Install Now to upload and install the plugin.



8. Activate the plugin by clicking on the Activate Plugin button.



You will also be prompted to enter your AIOS email and password to connect your site to licences. This will allow the plugin to receive automatic updates.

Yes, the free AIOS plugin should be installed before installing and activating AIOS Premium.

AIOS Premium includes the premium plugin to be installed on your site, plus licences for our Site Scanner service. You will also gain access to our premium customer support.

Yes, AIOS Premium is compatible with WordPress multisites. For multisite networks, the protection will apply to the network as a whole, and the dashboard and options will be available to Network Administrators.

There is no 100% guarantee that a security plugin will be able to protect against all attacks, as there is always the possibility of unknown WordPress vulnerabilities or other unexpected factors.

However, All-In-One Security gives incredibly comprehensive protection against known attack methods.

The plugin should be compatible with most hosts, unless the host has specifically restricted the use of security plugins. Similarly, certain features may not work on some servers, especially Windows/IIS platforms. Any feature that affects the ‘.htaccess’ file will not apply on a Windows IIS server.

Development and test sites require their own licence if updates to the plugin are needed.

However, these sites can be disconnected from the licence when they have served their purpose. You can disconnect the licence via the site’s WP Admin->Plugins page, and it will be available to be reassigned to a different site.

These shortcodes can be added to a dedicated page where your users can manage their TFA settings, including turning them on or off, viewing their QR code for scanning, and accessing emergency backup codes.

These features allow your users to take control of their account security without needing to navigate through complex settings. Plus, you can display the current authentication code directly on your site, making the login process easier.

The shortcodes are usually used in the site's backend. They are not intended to be publicly visible on your main website pages. Use them in the accounts section of your site when someone is already logged in.

The following shortcodes are available:

For free and premium AIOS users:

twofactor_user_settings : This shortcode will display the whole user configuration. Use this to allow your users to get/set their TFA settings. Alternatively, to design the page yourself, you can use the individual short-codes, following:

For premium AIOS users:

twofactor_user_settings_enabled : Display the option to turn TFA on or off.

twofactor_user_qrcode : Display the user’s QR code for scanning.

twofactor_user_emergencycodes : Display the user’s emergency codes.

twofactor_user_advancedsettings : Display the user’s advanced settings (e.g. selecting TOTP or HOTP).

twofactor_user_privatekeys : Display the user’s private keys. Use the ‘type’ parameter, with values ‘full’ (default), ‘plain’, ‘base32’ or ‘base64’ to control exactly what is displayed.

twofactor_user_privatekeys_reset : Display a link for the user to reset (change) their private key.

twofactor_user_currentcode : Display the current TFA code.

twofactor_user_presstorefresh : Wrap this shortcode around any HTML that you want to cause the current TFA code (displayed by the twofactor_user_currentcode shortcode) to refresh when clicked.

twofactor_conditional : Wrap this shortcode around any content that you wish to be displayed only if the condition is met. The condition is specified by the “onlyif” parameter, with valid values: activate, inactive, available, unavailable. The content will be shown depending on whether the user has TFA available (i.e. the administrator has allowed it for their user level)/activated. You can use this, for example, to display notices to your users to suggest that they activate TFA, or to remind them that it is available, etc.