@anvitha ash - I agree with everything the previous posters have stated, but here are a few more details about GRC roles in general.
The roles that begin with sn_grc.xxx. (with the exception of the business user roles) are roles that were created a long time ago when we didn't have separate compliance, risk and audit applications. When those apps were developed new more specific roles were created (sn_compliance.xxx, sn_risk.xxx, etc). If you look at the user, manager and admin roles of these, you will see that the sn_grc.xxx role is contained within it.
In the class I teach, we tell students to not directly assign the sn_grc.admin, manager and user role to groups/users. Because when you assign the compliance/risk role it will be inherited.
Fast forward to today where we have the GRC Business User role. This role was created because customers needed to give access to certain users to perform GRC actions, but they didn't want them to have as much power as the "user" role. They needed more than reader, but less than user.
On my next statements - I will qualify these statements - please check with your account rep to confirm that this is how it works for your instance. As an instructor, I try and stay away from licensing questions because there are too many variables for me to consider. But in general, on the Business User roles - the impact to licensing does not occur until the user has performed a GRC action. So, I could assign these roles to all managers in my organization but there would not be any licensing impact until a manager used the role to perform a GRC action - such as responding to an assessment.
Hope that helps.
