Access Controlled Button Bars
If it's not absolutely necessary, preventing a user from accessing parts of your software is a bit better than letting them know what's possible or what's hidden from them. It also allows a given group of users to focus better without presenting options which may not apply to the functions they perform.
In this video and technique file, we take a look at two tricks combined into one. We're making single segments of a button bar hide and show, without resizing, and we're doing this based on a user's collective security access.
If you've had a FileMaker solution grow to the point where all users still have access to all things, then you'll find some great information in this video about limiting access to certain features of your user interface. This video and technique file will give you the insight into providing a limited set of options based on the access levels you define.
Comments
icon
Matt
thanks...
better way to deal with the 'empty' segment is not to use conditional formatting (which needs to be calculated every time) but a 'blank' SVG as the icon..
To hide or not to hide
This is situational, but I find that it causes confusion to completely hide a button. In most cases I’ll add a disabled version. The disabled version (text is gray) is often a popover that does nothing, but its text explains why the function is not available. Saves me a custom dialog (which I try to avoid), and a trap in a script.
Alternative to tabs
Hi Matt,
would this be a good alternative to try to make tabs invisible? And then let the button do a "go to tab/object" kind of solution?
Or just make a portal and treat the tabs as records?
Regards,
Joost