Because Capture Analytics is primarily intended for executives, the default way to control access to the analytic data is based on the organizations to which opportunities are assigned. However, some firms want to provide Capture Analytics to managers and supervisors for whom security based on organization may not provide the necessary access. For example, you may want a project manager to only have access to data for the opportunities assigned to him or her. In addition, some firms do not assign opportunities to organizations, or do so inconsistently, making organization-based security unworkable.
In these cases, use Base Access On under Alternate Security to specify an opportunity field other than organization on which you want to base security for some or all Capture Analytics users.
The list of fields includes the following system fields:
Organization (OwningOrg in the Base Access On list)
Principal
Project Manager (ProjMgr in the Base Access On list)
Supervisor
It also includes the following types of user-defined fields (UDEFs):
Checkbox
Client
Dropdown
Employee
Lookup
Organization
This setting is for Capture Analytics security only. A similar feature is available in Costpoint Analytics to provide access to project analytics based on the project managers assigned to projects.
Before you implement alternate security, prepare the Microsoft® Excel file containing user access information and load that information into Capture Analytics. For more information, see Security Based on an Alternate Field: Key Concepts and related topics.
In Base Access On under Alternate Security, select the GovWin Capture Management field on which you want to base the alternate security.
In the CRMAnalyticsEmployeeSecuritySetup.xlsx file, specify the tab and data access for each user who will be subject to the alternate security. (See Specify Security Settings in the CRMAnalyticsEmployeeSecuritySetup.xlsx File.)
Load the security data into the Capture Analytics data model. (See Set Up and Maintain Security Based on an Alternate Security Field.)
This step creates a separate copy of Capture Analytics for each network user ID listed in the CRMAnalyticsEmployeeSecuritySetup.xlsx file. Each copy contains only the data that user can access, based on the alternate security setup information.
Normally, you do not change this setting after the initial configuration. If you need to, you can change it, but you must also then enter the appropriate field values for your users in CRMAnalyticsEmployeeSecuritySetup.xlsx and run the security load process to create the user-specific copies of Capture Analytics.