Controlling Access to VDL, JavaScript and Tableau Views

An interface can optionally specify a list of authorities that the user must possess in order for the view interface to be accessible.

This is particularly useful to control access to custom or Tableau views.

Note You control access to all views in a Tableau workbook (not individual views). Examples of custom or Tableau View configurations for access control are shown below.

Multiple authorities can be specified, separated by whitespace. The authorities required can be taken from the standard authorities (such as SCENARIO_EDIT), or any custom authorities.

Note The user will need to have all the authorities listed (though not necessarily in the same authority group) in order to access the view.

There is no restriction on what can be specified here. In particular, it is not enforced that the authorities listed in the companion file have to exist on the system.

Custom JavaScript View Example

<client>
    <view-group title="Main">
        <html-view title="Strategy Dashboard" authorities="PAYGRADE_CEO"
                   path="index.html"/>
    </view-group>
</client>

Custom Tableau View Example

<client>
    <view-group title="Main">
        <tableau-workbook authorities="SYS_USER DEVELOPER" 
		workbook="TableauTest"/>
    </view-group>
</client>

An app can specify the custom authorities it depends on in the companion file. These authorities will be created when the companion file is loaded with the app or via the developer update option, if they do not already exist, as shown below:

<model-companion
        xmlns="http://www.fico.com/xpress/optimization-modeler/model-companion" version="3.0">
	<custom-authorities>
		<custom-authority>PAYGRADE_CEO</custom-authority>
		<custom-authority>PAYGRADE_MANAGER</custom-authority>
		<custom-authority>PAYGRADE_ENGINEER</custom-authority>
	</custom-authorities>
</model-companion>

© 2001-2020 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.