Why Aegis does not support multiple roles per user

The number one feature request for our role-based permissions gem Aegis is support for multiple roles per user. It's also the one request we refuse to implement on a weekly basis.

Our belief is that you should only distinguish roles that have fundamentally different ways of resolving their permissions. A typical set of roles would be

  • anonymous guest (has access to nothing with some exceptions)
  • signed up user (has access to some things depending on its attributes and associations)
  • administrator (has access to everything)

We don’t do multiple, parametrized roles like "leader for project #2" and "author of post #7". That would be reinventing associations. Just use a single :user role and let your permission block query regular associations and attributes.

Update: Aegis now supports multiple roles per user

You can follow any response to this post through the Atom feed.

Avatar

Sat, 06 Mar 2010 11:40:00 GMT

by henning

Tags:

  • chugoboy said about 1 month later:

    Man, this is a nice looking site.

    Authorization objects in SAP (ABAPer) can be a real headache. I’m looking forward to learning how this is done using Aegis, but I just wanted to comment on the look of your site. Nice!

  • Henning said about 1 month later:

    Thank you chugoboy! I’m glad you enjoy our new look.

  • chugoboy said about 1 month later:

    Bitte.

    BTW: Aegis looks like it can be flexibly maintained to give exactly the functionality I need. Danke.

Leave a comment