Can anyone tell me, what&#39;s the real difference between group and role? I&#39;ve been trying to figure this out for some time now and the more information I read, the more I get the sense that this is brought up just to confuse people and there is no real difference. Both can do the other&#39;s job. I&#39;ve always used a group to manage users and their access rights.

Recently, I&#39;ve come across an administration software, where is a bunch of users. Each user can have assigned a module (whole system is split into a few parts called modules ie. Administration module, Survey module, Orders module, Customer module). On top of it, each module have a list of functionalities, that can be allowed or denied for each user. So let&#39;s say, a user John Smith can access module Orders and can edit any order, but haven&#39;t given a right to delete any of them.

If there was more users with the same competency, I would use a group to manage that. I would aggregate such users into the same group and assign access rights to modules and their functions to the group. All users in the same group would have the same access rights.

Why call it a group and not role? I don&#39;t know, I just feel it that way. It seems to me that simply it doesn&#39;t really matter :] But I still would like to know the real difference.

Any suggestions why this should be rather called role than group or the other way round?

All Rights Solutions on Gang of Coders

Total of 1 Rights Solutions

Group vs role (Any real difference?)