Oh, how I needed some humor today

I'd like a double-bacon cheese burger...hold the cheese and bacon. I'm trying to cut down on how much red meat I'm eating...

Aye, we'll look into adding that functionality as well.  Would you also like to hide the users, or maybe the roles node, too?

Down the road, could you also add the ability to hide restriction sets? I'm not using them with this application and although they could be handy for an end-user, it also adds uneeded complexity to this particular app.

Thanks

<shrugs> I dunno

Perfect...why can't other vendors work like you guys?!? Thanks a million.

We kept the Permissions node in the runtime version of the SecurityDialog so that the end-users could click on a permission and immediately see all of the roles/users assigned to that permission.  However, we agree that this should be a developer preference, so we added an overload to the constructor of the SecurityDialog that accepts a single Boolean value indicating whether you want to show the permissions node.  It's in the update that was posted yesterday.

Is it possible to hide the permissions node in the security editor when accessed from within my app? For obvious reasons, the end-user cannot modify these and the editor does disable new, modify, delete, etc.

To keep things simple, it would be nice to simply hide the node from the end user.