Permissions must be assigned to each User Account that is created. The Live Stats interface is divided into the following major categories. Permissions can be applied to each category on a per account basis:
| Who's On |
Live "Who's On" reports. |
| Usage |
Sessions, hits, kilobytes over time. |
| URLs |
Web Pages reports. |
| Browsers |
Web Browsers and Agents. |
| Referrers |
Who's referring to the Web site, by domain, URL, Search Engine, Keyword. |
| Origins |
Allow viewing of demographics reports. |
| Watches |
URL, IP and/or Click Thru watches. |
| Exports |
CSV exports. |
| Admin |
Virtual Server Administration interface. |
Assigning Permissions:
- First select the "User Permissions" option from the User Management branch.
- Setting Permissions is as simple as checking and unchecking report options for each Account. If a report is checked, that user can view it by entering their name and password. If it's not checked they will not be able to access the report even if they provide their account information.
It is recommended that the Admin interface for the Virtual Server be secure (no public access). In our example only John Smith can do administration. It is always recommended that the server administration interface be fully secured even on Web sites such as our site, www.mediahouse.com that allow public access to the Live Stats interface.
Note: The Statistics Server Global Admin account information can be entered at any User Name/Password prompt across the package to override Permission settings for Virtual Servers.
Note: Virtual Server statistics reports intentionally default to Public Access. For ISPs this is considered to be a feature, it creates a system where ISP customers can set their own permissions without having to involve the ISP every time they want to add or delete an account. In our example John Smith is the administrator. For ISPs with hundreds of Virtual Servers this can be a substantial timesavings.
Note: In order for Statistics Server to ask a user for their password, there must be at least one (1) user account configured with permission for that particular category and Public Access must not be allowed to that category.
Note: If you don't want anyone to have access to a particular section, you must create a dummy account and give it permission to that section.
|