Shortcomings of modelling roles as boolean columns on User table

I'm working on a Rails app using CanCan for RBAC and I only have 3 roles and maybe I'll add 1 or 2 more somewhere down the track.

In the past I've always had roles as their ow开发者_运维知识库n entity, joined to users via a m2m link-table. With so few, and static, roles, that seems like overkill. So I'm thinking of simply adding boolean columns to my Users table for each role. I could also use a bitmask (like the CanCan example does) but I'm not too keen on storing multiple values in a single column.

So my question is, what's the best thing to do in this situation: bitmasks, multiple boolean columns, or a properly normalized m2m relationship?

Operating on the principle of YAGNI would drive my decision to use the separate bit columns for each role. Even if you add a couple more columns over time it's still easier to manage than a m2m link-table. I completely agree with not using bitmasks as they obscure the meaning of the data.

I'm only addressing this from the SQL side as I have no experience with Rails, CanCan or RBAC.