Developer guide | RDocs | Screencast 1 | Screencast 2
CanCanCan is an authorization library for Ruby and Ruby on Rails which restricts what resources a given user is allowed to access.
All permissions can be defined in one or multiple ability files and not duplicated across controllers, views, and database queries, keeping your permissions logic in one place for easy maintenance and testing.
It consists of two main parts:
-
Authorizations library that allows you to define the rules to access different objects, and provides helpers to check for those permissions.
-
Rails helpers to simplify the code in Rails Controllers by performing the loading and checking of permissions of models automatically and reduce duplicated code.
![Goboony](./logo/goboony.png)
![Renuo AG](./logo/renuo.png)
Do you want to sponsor CanCanCan and show your logo here? Check our Sponsors Page.
Head to our complete Developer Guide to learn how to use CanCanCan in details.
Add this to your Gemfile:
gem 'cancancan'
and run the bundle install
command.
User permissions are defined in an Ability
class.
rails g cancan:ability
Here follows an example of rules defined to read a Post model.
class Ability
include CanCan::Ability
def initialize(user)
can :read, Post, public: true
return unless user.present? # additional permissions for logged in users (they can read their own posts)
can :read, Post, user: user
return unless user.admin? # additional permissions for administrators
can :read, Post
end
end
The current user's permissions can then be checked using the can?
and cannot?
methods in views and controllers.
<% if can? :read, @post %>
<%= link_to "View", @post %>
<% end %>
One of the key features of CanCanCan, compared to other authorization libraries, is the possibility to retrieve all the objects that the user is authorized to access. The following:
@posts = Post.accessible_by(current_ability)
will use your rules to ensure that the user retrieves only a list of posts that can be read.
The authorize!
method in the controller will raise an exception if the user is not able to perform the given action.
def show
@post = Post.find(params[:id])
authorize! :read, @post
end
Setting this for every action can be tedious, therefore the load_and_authorize_resource
method is provided to
automatically authorize all actions in a RESTful style resource controller.
It will use a before action to load the resource into an instance variable and authorize it for every action.
class PostsController < ApplicationController
load_and_authorize_resource
def show
# @post is already loaded and authorized
end
def index
# @posts is already loaded with all posts the user is authorized to read
end
end
Head to our complete Developer Guide to learn how to use CanCanCan in details.
If you have any question or doubt regarding CanCanCan which you cannot find the solution to in the documentation, please open a question on Stackoverflow with tag cancancan
If you find a bug please add an issue on GitHub or fork the project and send a pull request.
CanCanCan uses appraisals to test the code base against multiple versions of Rails, as well as the different model adapters.
When first developing, you need to run bundle install
and then bundle exec appraisal install
, to install the different sets.
You can then run all appraisal files (like CI does), with appraisal rake
or just run a specific set DB='sqlite' bundle exec appraisal activerecord_5.2.2 rake
.
If you'd like to run a specific set of tests within a specific file or folder you can use DB='sqlite' SPEC=path/to/file/or/folder bundle exec appraisal activerecord_5.2.2 rake
.
If you use RubyMine, you can run RSpec tests by configuring the RSpec configuration template like this:
See the CONTRIBUTING for more information.
Thanks to our Sponsors and to all the CanCanCan contributors. See the CHANGELOG for the full list.