Client Roles

Sigma enables you to assign different roles for the maker, checker and viewer users for your clients or customers, thereby enabling the listed maker, checker and viewer users to be assigned with the appropriate accessible roles based on their entitlements. On accessing Sigma Studio, the maker, checker and viewer users can respectively create, approve and view the various Studio components to which they are entitled and it is essential that the approval flow should be initiated, so as to enable the approval privileges for the checker user.

The role matrix of the Client Maker, Checker and Viewer users is provided as follows:

Role Category	Roles	Sigma Studio Privileges	Sigma Application Privileges
Client	OPS-OFFICE-MAKER	Can create, edit and delete the following: - Corporate customers - Application users - Solution packages - Client package mapping - Client criteria value mapping - Contacts - Client Grouping - Criteria Grouping - Criteria Group Mapping - Report Bursting	No access
	OPS-OFFICE-CHECKER	Can approve or reject the following: - Corporate customers - Application users - Solution packages - Client package mapping - Client criteria value mapping - Contacts - Client Grouping - Criteria Grouping - Criteria Group Mapping - Report Bursting	No access
	OPS-OFFICE-VIEWER	Can view the following: - Corporate customers - Application users - Solution packages - Client package mapping - Client criteria value mapping - Contacts - Client Grouping - Criteria Grouping - Criteria Group Mapping - Report Bursting	No access
	OPS-OFFICE-ADMIN	Can perform the following: - Re-run failed ad-hoc reports - Re-run failed scheduled reports	No access

For the Studio and Sigma Applications, integrated with the Intellect ARX authentication system, it is essential that you must have already created the user roles for the maker, checker and viewer client users in the Intellect ARX authentication system portal.

When you create the Client Maker, Checker and Viewer users in Intellect ARX, ensure that you select the appropriate User Type, Sub-Type, Entity and Role in the User Creation screen on Intellect ARX.

For the Client Maker ensure:

User Type must be Bank User
Sub-Type must be Functional User
Entity must be STUDIO and SIGMA
Role must be OP_USER, SIGMAGRP and OPS-OFFICE-MAKER

For the Client Checker User ensure:

User Type must be Bank User
Sub-Type must be Functional User
Entity must be STUDIO and SIGMA
Role must be OP_USER, SIGMAGRP and OPS-OFFICE-CHECKER

For the Client Viewer User ensure:

User Type must be Bank User
Sub-Type must be Functional User
Entity must be STUDIO and SIGMA
Role must be OP_USER, SIGMAGRP and OPS-OFFICE-VIEWER

The appropriate access controls should be provided to these roles in the Access Controls screen.

For OPS-OFFICE-MAKER, the Role must be OPS-OFFICE-MAKER
For OPS-OFFICE-CHECKER, the Role must be OPS-OFFICE-CHECKER
For OPS-OFFICE-VIEWER, the Role must be OPS-OFFICE-VIEWER

The System Administrator will approve the user details and the access controls provided to the client users assigned with different user roles on the Intellect ARX authentication system portal.

Once the client users with specific user roles are created in Intellect ARX, ensure that you provide appropriate entries in the CT_REQ_MDLR_AUTHFLOW table on the Studio schema.

The client maker, checker and viewer users can respectively create, approve and view corporate customers or clients, application users, solution packages, client package mapping, client criteria value mapping and management of user contacts in Sigma Studio. The client maker user will be able to access both the Sigma Studio and Sigma Applications, whereas the client checker and viewer users will be be to access only the Studio Application.. The client maker user will possess the privilege of an application user, while accessing the Sigma Application.

You can even create a standard client user in the Intellect ARX authentication system without assigning the checker and viewer roles, thereby ensuring that no approval flow gets involved.

To create a standard client user in the Intellect ARX authentication system, ensure:

User Type must be Bank User
Sub-Type must be Functional User
Entity must be STUDIO and SIGMA
Role must be OP_USER, SIGMAGRP and OPS-OFFICE-MAKER

The appropriate access controls should be provided to the standard OPS-OFFICE-MAKER role in the Access Controls screen on Intellect ARX.

For the standard OPS-OFFICE-MAKER, the Role must be OPS-OFFICE-MAKER

The standard client user can create corporate customers or clients, application users, solution packages, client package mapping, client criteria value mapping and management of user contacts in Sigma Studio. The standard client user will be able to access both the Sigma Studio and Sigma Applications. The standard client user will possess the privilege of an application user, while accessing the Sigma Application.

Apart from the standard client maker user, you can even create the standard client admin user to re-trigger the failed reports and report schedules. On accessing Sigma Studio as a client admin user, you will be able to see the lists of reports and report schedules, which had already failed to get generated in the Sigma Application.

For creating the standard client admin user in Intellect ARX, ensure:

User Type must be Bank User
Sub-Type must be Functional User
Entity must be STUDIO and SIGMA
Role must be OP_USER, SIGMAGRP and OPS-OFFICE-ADMIN

The appropriate access controls should be provided to the standard OPS-OFFICE-ADMIN role in the Access Controls screen on Intellect ARX.

For the standard OPS-OFFICE-ADMIN, the Role must be OPS-OFFICE-ADMIN

The standard client admin user can access only the Sigma Studio Application.

Perform the following step on the Studio schema:

In the CT_REQ_MDLR_AUTHFLOW table, change the type of authentication from noauth to foureye or sixeye and make changes to the AUTH_FLOW column accordingly. A sample entry is provided as follows:

TABLE COLUMN	VALUES
GCIF	CTSTUD2014ENTL
FLOW_CTRL_ID	007
PRODUCT	ENTL
SUB_PRODUCT	CLIENT
CHANNEL_ID	3
APPLICATION_ID	CTSTUDIO
DEFAULT_IND	Y
EVAL_CONDITION	{ condition : [ { id : equals , field : $context.authflow value : true } ] }
EVAL_ORDER	1
STOP_PROCESS_IND	FALSE
RESPECT_HIER_IND	FALSE
TYPE	foureye
AUTH_FLOW	{ authflow : [ { tier : [ { type : INTEGER, min : 10, max : 100, workflow : { type : foureye , flow : { completed : false } } }, { type : INTEGER, min : 100, max : 1000, workflow : { type : sixeye , flow : { completed : false } } }, { type : INTEGER, min : 1000, max : 10000, workflow : { type : tree , flow : { condition : OR , completed : false, flow : [ { role : A , count : 1, completed : false }, { role : B , count : 2, completed : false }, { role : D , count : 1, completed : false }, ] }, { completed : false, flow : [ { role : A , count : 1, completed : false }, { role : C , count : 1, completed : false }, { role : D, count : 1, completed : false } ] }, { completed : false, flow : [ { role : X , count : 1, completed : false }, { role : Y , count : 1, completed : false } ] }, { role : E , count : 1, completed : false } ] } } } ] } ] }

Refer the following pages for detailed information on the usage of the client maker, checker, viewer and admin user roles in Sigma Studio: