Jump to content
Server Maintenance This Week. ×

"Full" custom menus vs restricted menus with Privileges


Jonathan9

This topic is 6092 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Clearly since FM introduced custom menus, there is a bit of a clash between the options in Privilege sets, (to allow users to have "All", "Editing only" or "Minimum" available menu commands), and then providing proper custom menus for your solution.

Custom menus won't function fully unless users have "All" set in the available menu commands of their associated privilege set (i.e. custom menus are heavily disabled, and any new non-Filemaker related menus/menu items are completely unavailable.)

I assume everyone who is using custom menus, is now allowing users with custom menu access, "Full" menus in the privilege settings.

Is there any danger to this approach? The last thing any developer wants is a rogue user managing to bypass the custom menu and suddenly having access to Delete all and other lovely commands!

Link to comment
Share on other sites

Impossibility of deleting records should be set in the PrivilegeSet -> Records -> 'View only in all tables' or 'Custom privileges...'

In general, making a Custom Menu Set does not provide any security, only ease of use and amelioration of the user experience.

Real security is established by the Data Access and Design settings in the Accounts & Privileges area.

Success!

Link to comment
Share on other sites

Thanks Henk :

Yes I'm aware of that, I use privileges on everything, but obviously some users need deletion access (but never delete all in my experience!). Therefore I wanted to make sure that with custom menus set at startup via scripts (in my case), depending on the user level, there is no quick way (or any way) for a curious user with non-admin access to bypass them and switch to full standard menus, which don't run custom code and may have "delete all" options.

I think for many of us that have been developing since earlier versions (myself at starting at lowly v3!), especially in large systems where we have constantly migrated to new versions, many times the client doesn't have the budget for a full rewrite in the newer technology, so systems end up with compromises using various functions.

I'm also curious to see if these three old menu options in privileges: "all", "editing only" and "minimum" are now rarely used, being just throw backs to the older versions. I still firmly believe that some of these custom menu functions should be integrated in the privilege sets for certain defaults, although some believe not!

Link to comment
Share on other sites

This topic is 6092 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.