Zero-configuration GraphQL + Relay support for Rails. Adds a route to process GraphQL operations and provides a visual editor (GraphiQL) during development. Allows you to specify GraphQL queries and mutations as though they were controller actions. Automatically maps Mongoid models to GraphQL typ...

Resolves a breaking change in CanCanCan version 1.13.0 and above when using it with DraperDecorator

Integration layer between Protector and CanCan

Define an ability class for each of your models to separate authorizations.

Generates initial code for a devise install. Gives the options for oauth, using cancan, and creating a user tool to manage the users.

CanCanCan integration with Active Model Serializers

Simple authorization for RubyMotion. Inspired by CanCan and Pundit.

Guard your links with permissions

Implements CanCanCan's rule-based record fetching using Mongoid.

Implements CanCanCan's rule-based record fetching using neo4j gem.

Adds some simple methods to your decorators to make it easier to use with the CanCan gem

Implements CanCanCan's rule-based record fetching using neo4j gem.

Extends CanCan with dynamic, inheritable permissions stored in a database, with caching and multi-tenant refinements

ryanb's nifty-generators + i18n, blueprint, formtastic, declarative_authorization and cancan.

Add namespace for cancan authorization library

Includes cancan controller helpers in all netzke components.

cancan ability for views

CanCan[Can] just can't satisfy me

Because https://github.com/CanCanCommunity/cancancan/pull/370

Split up your CanCan Ability by allowing you to easily create abilities in separate classes which you reference in your main ability model. This is mainly useful if you want to break down your abilities into smaller classes for organizational purposes.'