The "Miscellaneous" form is a single form that contains various settings and options. They are small enough that they don't require their own forms, so they have been placed together within a single form.

The following is a brief description of each field:

1. Contact Name/Contact Email
 
This name and email address are used whenever nTreePoint sends email to users. It is used as both the From address of the email and as the signature of the body of the message. For example, if a user forgets her password and submits the form to have a new one emailed to her, this name and email address will be used.
2. Default Page Width and Page Padding
 
These two fields define the default page width and padding (both in pixels) used when adding new pages. These can be changed at the page level, but the initial values will be the values provided here. If the width is blank or zero, the actual page width will be 100%.
3. Meta Tags
 
Some search engines will use the contents of the meta keywords to index your site's content. You can provide default keywords that will be inserted into a meta keywords tag on every page that nTreePoint generates. The meta description will be used by search engines when your page comes up in a search result. This will be displayed along with the link to your site.
4. Disable Tree Map
 
The Tree Map, if enabled, will be accessible by all users from a link in the Header Bar. This view will show an expanded hierarchy of ALL sections, even if they are private. If, however, a user does not have access to one of the private sections and clicks the link to that section from the Tree Map, access to the section will still be denied. If you wish to disable this feature, check this option.
5. Headlines Label
 
The "Headlines" appear on both the Summary Page for each section and the My UMinfo Summary Page. (For more information about Headlines, see the Headlines section of the help system.) If you would like Headlines to be called something else (for instance, "Important" or "This Just In"), you can change the label to read anything that you'd like.
6. My Account Label
 
This is the label that appears whenever a user is logged in. Clicking this link in the Header Bar will take the user to his Summary Page where he will see his customized view of the information available within the nTreePoint. This label can be changed to reflect the group that is using the application. For example, in the screenshots for Unidigm University, the label reads "My Unidigm".
7. Hide User Address Fields
 
If you do not wish to collect address-related information from your users, you can hide the Address, City, State/Province, Country, and Zip/Postal Code fields in the Users form.
8. New User Account Login
 
You can assign a specific account that will serve as the default for the subscription settings for new users. Whenever a new standard account is created, it will automatically have the same subscription settings as this user (although the new user can change these if desired after logging in for the first time).
9. Show User Name When Logged In
 
You can choose to show or hide the users' names in the top-left corner of the screen when they are logged in. Additionally, if the Show User Name when Logged In checkbox is checked, you can provide additional text that will appear before and after the current user's name. For example, If the Caption Before is "Hello " and the caption after is "!", and the user's name is "Dave Jackson", the complete text would read "Hello Dave Jackson!"
10. Enable My Account Features
 
If this checkbox is unchecked, users will still be able to login to the application (for example, as Section Owners to add new information to the various tools), but they will not have the ability to customize their own view of the application, to subscribe to the email features, or to update their account information.
11. My Account vs. Summary Page of Top Section
 
This determines which page a user will see after she logs into the system. If "My Account" is selected, the user will be taken to her own custom Summary Page. If "Summary Page of Top Section" is selected, the user will be taken to the Summary Page of the top section in the section hierarchy.

Note: Administrators are always taken to the default page in the Admin section after logging in.

12. Post-Login URL
 
You may provide a post-login URL instead of sending users to their My Account page or the summary page of the top section. If provided, all users will be taken to this page after logging in. The URL must be a valid page within nTreePoint, so the URL must begin with "index.asp".
13. Mail Pickup Path
 
In order for the email features of the application to function properly, the Simple Mail Transport Protocol (SMTP) service must be installed and running; however, it does not to be installed on the same server as the application itself. If you would like to use a separate machine to handle the mail that is sent from the application, this is possible. The contents of this field should be the path to the "Pickup" folder of the SMTP service. The service checks this folder periodically for new mail and, if there is any present, sends it. This application writes its email directly to that folder, so it needs to know the full path for the folder's location. If the SMTP service is installed on the same machine as the application, then it is most-likely under the "inetpub\mailroot" folder. For example, "c:\inetpub\mailroot\pickup". If the service is running on a different machine, you will need to enter the full network path to the folder or map the folder to a drive letter on the local machine and then use that as the path.
14. Install Path
 
This is the folder that nTreePoint was installed to when the setup program was originally run. This field will be set when the application is originally set up, so you should not need to change it, but should you need to move the location of the application for any reason, you can change the location here.
15. Cache Path
 
Some pages that are frequently accessed and that take more time than other to process (for example, the Summary Page for each section) are cached to disk to improve performance. The Cache Path is the folder that these files should be stored in. By default, this will be the "Cache" folder in the nTreePoint installation folder.
16. Cache Timeout
 
This is the amount of time, in hours, that can pass between successive reads of a cached file. If a file has not been read for more than this duration of time, the cached file will be deleted. It is recommended that this value be as high as possible.
 
The following section details fields that can be used in order to force the logins that users choose to meet certain criteria. This is an advanced feature, and uses an advanced method to provide this functionality. If you have never heard of "Regular Expressions" or are unfamiliar with their syntax, the following fields should be left blank. If you need to set limitations on what logins users can choose, please consult with someone who is familiar with Regular Expressions or study this documentation.
 
20. Login Must Match/Error Message
 
Here, you can provide a regular expression that will be checked against the login that is chosen by a user when an account is created (or when the login is updated by the Administrator). If the login does not match the regular expression, the text in the Error Message field will be displayed to the user and he will be required to make the appropriate changes to his chosen login. In other words, the user's login must match the regular expression.

If a regular expression is provided, an error message is required. If a regular expression is not provided, this field is ignored when a login is added or updated.

21. Login Must Not Match/Error Message
 
Here, as with the Login Must Match field, you can provide a regular expression that will be checked against the login that is chosen by a user when an account is created (or when the login is updated by the Administrator). Here, however, if the login does match the regular expression, the text in the Error Message field will be displayed to the user and he will be required to make the appropriate changes to his chosen login. In other words, the user's login must not match the regular expression.

If a regular expression is provided, an error message is required. If a regular expression is not provided, this field is ignored when a login is added or updated.