Simple authorization solution for Rails which is decoupled from user roles. All permissions are stored in a single location.

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

Like i18n_shoulda_generator, but with implemented cancan. It is mainly used toether with the starter-template_w_cancan.rb

This is a basic Rails engine utilizing Authlogic, CanCan and Easy Roles to create a starting point for simple Rails-based applications that need authentication and authorization.

Provides assistance for setting up an auth solution using devise and cancan auth frameworks

Role specific Permits for use with CanCan permission system

Guard your links with permissions

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.'

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

Add namespace for cancan authorization library

Simple authorization solution for Rails which is decoupled from user roles. All permissions are stored in a single location. This project is based off of Ryan Bates's CanCan Gem.

CanCan extension that adds some real-deal syntax and file organization lovin'!

Authorizer is a gem for Ruby (in conjunction with Rails 2.3) that does authorization for you on a per-object basis. What makes this gem different from e.g. declarative_authorization and cancan is they define one role for the entire application. With Authorizer, you define roles for different users on every Rails object. Let's use a Dropbox analogy. With Dropbox, you can choose which folder you want to share. For instance: Al has a home folder with these subfolders in it: - Music (shared with Bob) - Pictures (shared with Casper and Bob) - News (shared with no-one) This causes Al to have all 3 folders in his Dropbox. Bob has 2 and Casper has only 1 folder called Pictures. In other words, a user has access to a subset of the entire collection of folders. Bob has access to 2 of Al's folders, namely Music and Pictures. But he doesn't even see the News folder, nor can he download files from it. Bob's access to the two folders is both read and write, so let's call that role "admin". Al is the owner of all 3 folders and has a role called "owner". This leads to the following Roles table: folder_name user_name role Music Al owner Bob admin Pictures Al owner Bob admin Casper admin News Al owner Now if we would allow Bob to also access the News folder but only read from it, we could add the role called "reader" to the table: folder_name user_name role News Bob reader This is exactly what Authorizer does for your Rails application.

Padrino can can use all CanCan goodies

Wraps CanCan and RoleModel up to make role based authorisation really easy in Rails 3.x.

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

cancan ability for views

Allowy provides CanCan-like way of checking permission but doesn't enforce a tight DSL giving you more control

Create a Rails app with authentication, authorization using Devise and CanCan

This gem preps a new Rails app with some of the best Rails gems and Jquery sweetness available( Twitter-Bootstrap, Devise, CanCan, Rails Admin, Spreadsheet, ) Not only does it takes care of the installation of these gems, it also extends your scaffolds to give aesthetically improved views. Further, apart from the standard scaffold views, it also creates an AJAX driven integrated view for your scaffold. It dries up your controllers and makes your models friendlier by adding schema stubs and standard validation options. Expect Cucumber integration in our next version