authorizable

A gem for rails giving vast flexibility in authorization management.

Features

• Customizable Permissions
• Permissions are all defined in one place
• Role-Based
• Easy UI Generation
• Categorization for Organizing Permission in the UI
• Easily Extensible (e.g.: adding support for permission groups )
• Automatic controller response upon unauthorized status
• Controller response is customizable
• Controller behavior defined in one place (optionally in the controller)

Installation

Gemfile

gem "authorizable"

Terminal

gem install authorizable

Configuration

Defining permissions

There are a couple ways that permissions can be defined.

If you like calling methods for configuration:

module Authorizable
  class Permissions
    can :delete_event
  end
end

will create a permission definition called delete_event which can be accessed by calling user.can_delete_event?(@event)

module Authorizable
  class Permissions
    can :edit_event, true, "Edit an Event", nil, ->(e, user){ e.user == user }
  end
end

will create a permission definition called edit_event with an additional condition allowing editing only if the user owns the event

Authorizable::Permissions.set(
  edit_organization:   [Authorizable::OBJECT, true],
  delete_organization: [Authorizable::OBJECT, [true, false], nil, ->(e, user){ e.user == user }, ->(e, user){ e.owner == user }]
)

This is how Authorizable references the permission definitions internally, just as raw permission: definition sets. Note that Authorizable::Permissions.set overrides the definitions list each time.

Customizing roles

coming soon...

Supporting group-based permissions

coming soon...

Why not CanCan?

Initially, I wanted something more customizable and that could aid in the generation of a UI where users can customize permissions for various groups or organizations. My goal is to at least support everything CanCan has, but with the mindset and intention of customizing behavior and remaining DRY.

Contributing

1. Fork the project
2. Create a new, descriptively named branch
3. Add Test(s)!
4. Commit your proposed changes
5. Submit a pull request