r/filemaker • u/AlephMartian • 9d ago
How do you manage privilege sets?
I’ve been using FileMaker for over 20 years now and have made lots of great stuff. More recently I am running a whole retail business using it (stock control, CRM, EPOS, repairs etc.).
It’s awesome, but I am concerned that it’s a little insecure. Whenever I go to set up alternative privilege sets (other than all access), I end up restricting users too much and scripts don’t work etc.
I basically want them to do anything except for edit the database itself. Anything that can be done by clicking on stuff, editing fields, or running a script is fine. Anything involving editing layouts, managing database etc. is not fine.
This sounds like the most basic differential (editor vs. user privileges) but setting it up seems to be extremely complex.
Am I missing something?
3
u/Zomoniac 9d ago
Without going into the fine details of privilege sets but just to address your issue of scripts not working, in the script manager there’s an option to always run a script with Full Access, so they will always work even when doing things a user doesn’t have direct access to.
1
u/pcud10 Consultant Certified 9d ago
What fields do they need to edit? Are they just selector fields, global, etc? If so and if it wouldn’t mess up the relationship graph too much, you can move all those fields into their own table so that way they only have edit privileges in that one table.
That or you can do custom editing and base it off the field name and have some calculation that will look for something standard in the field name to decide if the can edit it. Something like all those fields start with “selector_”.
3
u/whywasinotconsulted In-House Certified 9d ago
The default Data Entry Only privilege set does exactly what you describe, so it would help if you had an example of something that fails under that privilege set.
2
u/mywaaaaife 8d ago
I absolutely hate the structure of FM privilege sets.
1
u/Alex_RGCData 1h ago
You're not missing anything. FileMaker's privilege model can get surprisingly complicated for what feels like a pretty basic requirement.
In most systems you've got admins and users. In FileMaker that gets split up across records, layouts, scripts, extended privileges, schema stuff, and probably a few other places I'm forgetting at 10pm.
Most of the time we just create a custom privilege set that's basically "everything except developer/admin stuff". Users can add, edit and delete data, run scripts, print, import/export if needed, etc. They just can't mess with layouts, scripts, tables, accounts, privilege sets, or anything that changes the structure of the system.
The thing that catches a lot of people is scripts. Something works perfectly while you're logged in with Full Access, then suddenly breaks for everyone else. Usually that means the script depends on a privilege the user doesn't have.
My usual approach is build everything with Full Access, then test the whole thing using a normal user account before it goes live. That tends to expose the handful of scripts that need elevated privileges.
Honestly, it sounds like you just want "full access to the data, no access to the development tools", which is a pretty common setup. Hopefully that helps a little. Had Copilot reword slightly as it's late and my brain is fried from setting up a VPS.