Page History
...
- Local administrator access on the CardioLog application server.
- "db_owner" on the CardioLog database. This is granted automatically by the installer.
- Optional: "processadmin" role on the CardioLog SQL server. This is used to allow end users to cancel queries (cancel loading of reports).
- Optional: "view server state" permission on the CardioLog SQL Server. This is used to collect internal SQL statistics on the CardioLog database performance, such as the current database size, index fragmentation rates, and I/O rates.
- "db_datareader" access on the SharePoint config and content databases is required for SharePoint Online environments only.
- Read access to the SharePoint TEMPLATE directory is required for SharePoint Online environments only.
- Site Collection administrator permission is required for SharePoint Online environments only.
- Member of the local IIS_WPG group access is required for Windows Server 2003 only.
- The Administrator role in CardioLog, which is granted automatically by the installer.
- Full Control permissions for the CardioLog Installation Folder, which is granted automatically by the installer.
- Permissions for starting and stopping the CardioLog services are required only if the selected user account is not a local administrator on the CardioLog application server.
If you would like run the Configuration Wizard after installation, the following permissions and roles are required for the user account which runs the CardioLog Analytics Configuration Wizard for SharePoint on-premise environments:
- SharePoint farm administrator, a local administrator on the SharePoint application server and WFEs and "db_owner" on the SharePoint config database are all required, but only if you are deploying the JavaScript tracking code through a SharePoint feature.
- Write access to the SharePoint TEMPLATE directory is required only if adding the JavaScript tracking code to SharePoint init.js file).
The TEMPLATE directory is usually found in these paths depending on your version of SharePoint:
[SharePoint 2013 Server]\%PROGRAMFILES%\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE
[SharePoint 2010 Server]\%PROGRAMFILES%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE
[SharePoint 2007 Server]\%PROGRAMFILES%\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE
Creating a share is recommended - \\sharepointservername\XX\TEMPLATE.