SMF Development > Applied or Declined Requests
Specific member permissions
Dan_y2k:
Or Member specific permissions. ;)
I know it's been asked before. But it is important. What if you have a member in a certain membergroup, that you don't want to allow him to enter a specific board? Your solution is to move it to another group that isn't allowed to enter to that board. But what if I want to do it to different, let's say 10, members, and disallow them from entering to different boards? That means I'll have to create 10 membergroups.
I have a membergroup named "Customers", and inside the main board they're allowed to enter, there are sub-boards that I would like to block them from entering. Let's say a member bought Product 1, and Product 3. I want him to be able to enter the corresponding sub-boards - Product 1, and Product 3. I don't want to allow him to enter Product 2 board, because he's not allowed to (didn't purchase that product for example). Because I can't set specific member permissions, the solution (which isn't helping me) is to allow him to view all products sub-boards. I won't open 3 (for the example) membergroups just for that.
That's why I think specific member permissions are so important.
Thanks for hearing me out. :)
Kindred:
The problem with that is - with the number of permissions in SMF, a member specific permissions system table could be larger than the members table itself.
individual permissions work well for systems with limited permissions to begin with i.e. access A, Access B, access C) but not well with something that has the existing granularity of SMF's permissions.
I see what you are saying and see the point of the concept, but, coding wise, I don't think it's worth the effort.
Dan_y2k:
So, why not create a member-specific table on demand?
I mean - if you use the member specific permissions on a certain member, create a table for him only.
For example, in the database there can be a table, called let's say "smf_custompermissions", and if I use the Member-specific permissions for the user Dan, then the only table data that will be there will be Dan's table (that will contain Dan's details related only to specific permissions). So the "smf_custompermissions" will be like a "mini-database", consisting of only users with custom (specific) permissions.
IchBin™:
I'd suggest you get someone to do this as a mod and see if it's something that will be useful for more than just a small subset of people. I'd personally never use such a permission. But if it turns our the mod is quite popular then it should be considered.
Dan_y2k:
I really think it can be useful to everyone.
But you're the developer.
Thanks anyways.
Navigation
[0] Message Index
[#] Next page
Go to full version