Pundit VS Action Policy

Pundit Gem on GitHub How to Create Different Permissions Across Users Using Pundit — Ruby on Rails Implementing Roles and Permissions in Ruby on Rails

If you come from the Rails world, you might be familiar with some gems that provide APIs to handle this, the most popular ones being cancancan and pundit.

For a specific example: if you're starting learning ruby, the pundit library is a good starter.

A very common pattern in Rails development is for a view to contain checks for things like current_user.can?(:take_some_action). These types of checks are common, especially in B2B applications that implement role-based permissions powered by a solution like Pundit.

authorization with pundit

Right now, all access control is done using Pundit and since most things are server side rendered, not only are the API endpoints authorized by Pundit policies, but some UI components conditionally render based on these policies as well.

Strong parameter assignment via Pundit

You may ask what's makes Active Entry better or different from other gems like Pundit, Action Policy (especially), or CanCanCan.

This is called “authorization”. pundit is a great library for it.

I also use the Pundit gem in all of my projects to enforce and centralize user access control and access-restricted ActiveRecord scopes. I can't recommend it highly enough. This gem will address your security and access control concerns in a very flexible way. What more, it is highly useful when used in the context of service objects and other plain Ruby classes within and outside of Rails applications.

You may ask what's makes Active Entry better or different from other gems like Pundit, Action Policy (especially), or CanCanCan.

At work, we've recently faced similar issues and moved to ActionPolicy as a result. It's designed slightly differently, but there is a lot of overlap with what John came up with.