While GorillaStack ships with three standard user roles, we have highly customisable role based access control. Users can define inheritance between roles and define policies that either allow or deny privileges on different resources. For example, a team may decide that they only want to give their Developers read only access, with additional privileges to manually execute their rules, as well as snooze or cancel them if they are schedule based. Using GorillaStack they could create a new role named 'Developer' which inherits from 'Guest', and create an
allow policy on
Rules, allowing privileges of
denyand then a resource type and a combination of privileges for that resource that you wish to allow or deny over that given resource.