IRM/ GRC - subscription "allocation" calculation

carlosgaspa
Tera Contributor

‎09-08-2024 04:34 PM

Hi,

 

I am trying to understand how SN user management calculates the "allocation" of GRC Operator and Lite Operator. I notice in the allocation report the following reasons are given (I dont know if there are any other). Can somebody tell me what they mean. I think I know the first two but want to hear from others:

 

  • User has the Operator role : sn_risk_workspace.IT_risk_manager 
  • User has the Operator role : sn_grc.business_user
  • User has the Lite Operator role : sn_compliance.reader (why is this not in the Lite Operator report)
  • The user gets assigned with risk assessment instance.
  • User performed CRUD operation on GRC tables. For more information, check Usage Data for Applications table. (How can this occur if the user does not have any GRC roles?)
0 Helpfuls
  • 1,079 Views
2 REPLIES 2

sathish_k
ServiceNow Employee
ServiceNow Employee

‎09-25-2024 02:00 AM

 

In GRC, License consumption is based on the roles assigned to users. There are primrily 2 types of roles(Operator and Lite operator). If a user is assigned with operator role, he/she will be charged for Operator license and if a user is assigned with only lite operator roles, he/she will be charged for Lite operator license. The “sn_irm_shared_cmn_licensing_role_type” contains list of all licensable roles in GRC and their role types i.e operator or lite_operator

 

1, 2 —> sn_risk_workspace.IT_risk_manager and sn_grc.business_user roles are of type operator. Hence these users are accounted for using Operator license

3 —> sn_compliance.reader is a lite_operator role. Hence this user is accounted for using Lite operator license if this is the only role assigned to the user. 

4 —> Whenever risk assessment is assigned to a user, the user will be charged as GRC Lite operator.

5 —> Customers can actually customise the acls on GRC tables by adding their own custom roles as per their requirements to use the GRC product. In this case, customer interacts with GRC tables using custom roles. Then in this scenario, users will be charged as GRC operators if they are doing CRUD operations on GRC tables.