Each module can be activated trough a rule, using user session information. These rules can be set trough Manager: <code>General Parameters</code>><code>Portal</code>><code>Menu</code>><code>Modules activation</code>.
</p>
<p>
You can use <code>0</code> or <code>1</code> to disable/enable the module, or use a more complex rule. For example, to display the password change form only for user authenticated trough LDAP or <abbrtitle="Database Interface">DBI</abbr>:
<h2class="sectionedit3"id="categories_and_applications">Categories and applications</h2>
<divclass="level2">
<p>
<ahref="configvhost.html"class="wikilink1"title="documentation:2.0:configvhost">Configuring the virtual hosts</a> is not sufficient to display an application in the menu. Indeed, a virtual host can contain several applications (<ahref="http://vhost.example.com/appli1"class="urlextern"title="http://vhost.example.com/appli1"rel="nofollow">http://vhost.example.com/appli1</a>, <ahref="http://vhost.example.com/appli2"class="urlextern"title="http://vhost.example.com/appli2"rel="nofollow">http://vhost.example.com/appli2</a>).
</p>
<p>
In Manager, you can configure categories and applications in <code>General Parameters</code>><code>Portal</code>><code>Menu</code>><code>Categories and applications</code>.
<liclass="level2"><divclass="li"><strong>rule</strong>: specify a <ahref="writingrulesand_headers.html"class="wikilink1"title="documentation:2.0:writingrulesand_headers">rule</a> or “sp: <name>” where “name” is the key name of the service provider, the corresponding rule will be applied <em>(available for <abbrtitle="Central Authentication Service">CAS</abbr>, <abbrtitle="Security Assertion Markup Language">SAML</abbr> or OpenID-Connect)</em></div>
<divclass="notetip">The chosen logo file must be in portal applications logos directory (<code>portal/htdocs/static/common/apps/</code>). You can set a custom logo by setting the logo file name directly in the field, and copy the logo file in portal applications logos directory