The access control settings allows you to set up the conditions that must be met to make the custom page accessible. Examples could be that the acting user is logged in, that the content being viewed is of a particular type, or that the acting user has permission to edit the viewed node. Which conditions can be used depends on the available contextual objects. If there are two user objects available, for example, the array of conditions will include user: compare.

A select list will show you which types of conditions are available. Any existing conditions can be edited by clicking the corresponding gear button and erased by clicking the button with a cross on it. (See figure 13.4)

Figure 13.4: Access control decides when a custom page as a whole should be visible.

How can this be used?
A custom page with the path admin/content/comments/spam could have access settings only letting users allowed to administer comments to reach the page.
A custom page with the path node/%node/comments could have access settings only making the page accessible only if the viewed node is an article.

TIP: Links leading to pages that you are not allowed to visit will normally not be displayed. This is a feature making it possible to use access rules to make custom pages appear as tabs only on nodes of selected types.

TIP: Access control for nodes, users and terms are set by their respective modules and the access settings in Page manager are skipped.

TIP: The acting user will always be available as an object when configuring access control.