It is recommended to create a dedicated user account for the CardioLog application. By default, the user who installs the application will be given administrator permissions.
Setup User Account Permissions
In order to fully run the CardioLog application, the following permissions and roles are required for the primary user account:
- A local administrator on the CardioLog application server.
- Permissions to "create any database" and "alter any login" on the SQL Server that hosts the CardioLog database are required for installation.
CardioLog Service Account Permissions
The following permissions and roles are required for the user account which runs the CardioLog application on a regular basis (the user account is selected during the installation):
- 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 (eg,. report loading).
- 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.
- Full Control permissions for the CardioLog Installation Folder, which is granted automatically by the installer.
- The Administrator role in CardioLog, which is granted automatically by the installer.
- db_datareader on the SharePoint config and content databases
- 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.
- Read access to the SharePoint TEMPLATE directory.
- 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.
The following permissions and roles are required for SharePoint Online environments only:
- A user account with the SharePoint Administrator role in Office 365 Admin Center, found under Customized Administrator when editing User Roles in MS Office 365.