As aforementioned, the <DisseminoWebsite> attributes of adminpath, adminuser and adminpass are compulsory and are respectively, the administrator login form URL, the administrator username and the administrator password. While it is obvious why adminpass is configurable making adminuser configurable improves security or at least it will if you avoid calling it 'admin' or similar. Likewise the adminpath. If that was always /admin people could find it and have a go at getting in. Call it something memorable but totally rediculous like /yohohoandabottleofrum then that gets to be a liitle bit harder.

The administrator account is completely separate from that of any users the site may or may not register and does not belong to any user class. Likewise, the administration facility is standard and cannot be configured to match the look and feel of the site. In a future version this will change since without being able to program the admin page, it is not possible to program in any application specific data manipulation tools. The administration login process is also different from that of registered users in that no cookie is issued. Instead Dissemino marks the IP address as being that of the current administrator login, with the inherent (and deliberate) limitation that only one administrator login can be in force at any one time.

The administrator login gives you the administration menu - which grows with every release of Dissemino but is still we admit, rather limited. Primarily the administration menu is and for security reasons will largely continue to be about providing system information rather than facilitating data modification or the enabling or disabling of particular users or aspects of particular user accounts. Only in bespoke implimentations would this differ.

The current administration menu is as follows:-

 1 ...   Show Memory Usage
 2 ...   Show Visitor Summary