RolePlays turns a policy into one readable class per resource, built and asked explicitly the way Pundit and Action Policy policies are, with its rules declared rather than defined method by method as in CanCanCan: every role declares the actions it may take, the attributes it may submit and the scopes it may read, all resolved with a shared :any fallback. The policy is told the role name rather than a user, so the same rules answer for a request, a background job or a spec.