Intranet Licensing
This field on the Sites or Sites/Entities form is enabled only if the current site is associated with an intranet that has a designated master site. Intranet licensing allows license administration to be managed for all sites from the master site (using the License Management form). Even though the license is applied only at the master site, users still need to be set up in all sites to which they have access. For instructions on setting up intranet licensing for a multi-site system, see the Multi-Site Implementation Guide.
If you change the value of this field for a site while users are logged into the site, the users will experience connection problems. Make sure all other users are logged out before changing this value, and then log yourself out after making the change.
If you decide to use intranet licensing, you should consider it a long-term situation. Turning it on and off can cause problems or just more work for you. The purpose of intranet licensing is to make managing licensing (use of the License Management form) easier. If you have intranet licensing on for a site and then decide to turn it off, you must generate and apply a license document to that site. You must then assign users of that site the appropriate licensed modules on the Users form. Also, when intranet licensing is on, new custom forms created and/or forms copied to other names must have the appropriate license module records created in the site where the form was created/copied and in the designated master site. Other intranet licensed sites will not have these records in their application databases. As long as intranet licensing is on, this is not a problem because all checking is done against the master site application database. If intranet licensing is turned off (on a site that is not the master), any forms created and/or copied from other sites in the intranet will not be licensed on that site (even after applying a new license document). This is because the appropriate license module records for those forms will not exist in the application database.