In order to implement access restrictions to several pages, you normally would have to open each of the pages and apply the Restrict Access To Page server behavior, based on user name and password and/or level for each. If all of these pages must share the same restriction settings and are located inside the same folder, MX User Login provides a quicker way: Restrict Access To Folder.
The end result of this command is similar to the Restrict Access To Page one, when viewed on a single page. The difference lies in the fact that this command applies itself to several pages at the same time. Only pages that have the same extension as required by the server model you're working on will be processed, and not all files in the respective folder (e.g. images, text files etc.).
The Restrict Access To Folder command is accessible from the MX Kollection tab of the Insert bar.
Note: Due to some technical reasons, Restrict Access To Folder can only be opened from this location. It cannot be accessed from the Server Behaviors tab in the Application panel, the MX Kollection entry.
To block users that are not logged in and do not have the required access
level from entering pages from a specified folder, follow the next steps
when configuring the command. It has two tabs.

To set the dialog box options for the first tab, follow the next steps:
In the Folder to protect text box enter the folder containing the site pages to protect. Use the Browse button to navigate through the site's structure and select the desired folder.
After you select a folder, all the files that
are to be processed are displayed in the grid below, and the path is displayed
in the Folder to protect text box.
Note: Access is restricted only for the files that have the
extension (.php, .asp,
.cfm) corresponding to the server model used.
For example, .jpg files will not benefit from
the command's effect.
Note: If you use this command on the
ColdFusion server model, a file named Application.cfm will be automatically generated in
the site root folder. Do not delete this file, as it contains settings
related to session variables used by the command and the current application.
If you remove this file or modify it, application pages that use sessions
will not function properly.